From: "Jörg Schaible" <joerg.schaible@bpm-inspire.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: stable gcc 5.4.0 ??
Date: Tue, 18 Apr 2017 11:16:17 +0200 [thread overview]
Message-ID: <od4ln4$a1r$1@blaine.gmane.org> (raw)
In-Reply-To: CAG6MAzSUqBS-qzRmETT3u48B=KXBQ0KjMQPqXLO=JDBmKjiv+g@mail.gmail.com
Hi Tomas,
Tomas Mozes wrote:
> On Tue, Apr 18, 2017 at 10:15 AM, Jörg Schaible <
> joerg.schaible@bpm-inspire.com> wrote:
>
>> Hi,
>>
>> according the logs, gcc 4.5.0-r3 is stable for amd64:
>> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-devel/gcc?showmsg=1
>>
>> However, after synching the tree, this version is still unstable for me.
>> Looking at the packages overview, it becomes even more weird, because
>> there seem to be two 4.5.0-r3 versions, one stable for amd64 and one
>> unstable: https://packages.gentoo.org/packages/sys-devel/gcc
>>
>> Can someone shed some light on this?
>>
>> Cheers,
>> Jörg
>>
>>
>>
> On which platform do you have it unstable? The packages problem is
> probably related to:
> https://bugs.gentoo.org/show_bug.cgi?id=612178
Amd64.
Yes, it might be the same problem. The ebuild for gcc-4.5.0-r3 on my machine
lists amd64 as unstable after synching the tree while the ebuild available
over packages.gentoo.org has a stable version in KEYWORDS.
Even if some GIT mirrors might be out of sync, it does not explain why
https://packages.gentoo.org/packages/sys-devel/gcc lists the same version
more than once.
Cheers,
Jörg
next prev parent reply other threads:[~2017-04-18 9:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 8:15 [gentoo-dev] stable gcc 5.4.0 ?? Jörg Schaible
2017-04-18 8:37 ` Tomas Mozes
2017-04-18 9:16 ` Jörg Schaible [this message]
2017-04-18 9:44 ` [gentoo-dev] " Mart Raudsepp
2017-04-18 11:07 ` M. J. Everitt
2017-04-18 12:44 ` Tomas Mozes
2017-04-18 13:12 ` [gentoo-dev] " Jörg Schaible
2017-04-18 13:27 ` James Le Cuirot
2017-04-18 13:38 ` Aaron W. Swenson
2017-04-18 14:12 ` [gentoo-dev] " Jörg Schaible
2017-04-18 14:40 ` [gentoo-dev] " Tomas Mozes
2017-04-18 14:41 ` [gentoo-dev] " Tomas Mozes
2017-04-19 7:31 ` [gentoo-dev] " Jörg Schaible
2017-04-19 9:22 ` Tomas Mozes
2017-04-19 18:25 ` Walter Dnes
2017-04-20 5:36 ` Tomas Mozes
2017-04-20 22:17 ` Walter Dnes
2017-04-20 22:51 ` Mart Raudsepp
2017-04-20 22:52 ` Matthias Maier
2017-04-21 1:44 ` Walter Dnes
2017-04-21 16:21 ` [gentoo-dev] " Jörg Schaible
2017-04-21 19:29 ` Francesco Riosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='od4ln4$a1r$1@blaine.gmane.org' \
--to=joerg.schaible@bpm-inspire.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox