From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "stack-protector-strong" option results in gcc error
Date: Tue, 23 Sep 2014 09:33:45 -0400 [thread overview]
Message-ID: <542176B9.8080100@gentoo.org> (raw)
In-Reply-To: <20140923085403.GA4540@waltdnes.org>
On 09/23/2014 04:54 AM, Walter Dnes wrote:
>
> Gentoo stable appears to be gcc-4.7.3-r1. ebuilds up to gcc-4.9.1 are
> present in the tree. Upgrading gcc is painful, so I appreciate the
> maintainers not forcing a rebuild with every version bump. That's the
> philosophy behind "stable". The tradeoff is that we have to wait longer
> for "new and shiney" stuff. For those who want it, you can always
> keyword a later version of gcc.
>
Stabilization of GCC is especially careful because if your GCC winds up
broken, you might not be able to fix it (emerge won't work).
And since GCC is used to build everything else on your system, it can't
go stable until all upstream packages are fixed or patched to work with
the new GCC.
There's usually a tracker for those packages. For gcc-4.9 it's at,
https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.9
next prev parent reply other threads:[~2014-09-23 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 2:49 [gentoo-user] "stack-protector-strong" option results in gcc error Walter Dnes
2014-09-23 6:16 ` Alexander Kapshuk
2014-09-23 8:54 ` Walter Dnes
2014-09-23 9:41 ` [gentoo-user] " Nikos Chantziaras
2014-09-23 10:09 ` [gentoo-user] " Neil Bothwick
2014-09-23 13:33 ` Michael Orlitzky [this message]
2014-09-23 14:07 ` Hinnerk van Bruinehsen
2014-09-23 11:52 ` Hinnerk van Bruinehsen
2014-09-23 12:47 ` Rich Freeman
2014-09-23 13:06 ` J. Roeleveld
2014-09-23 14:07 ` Hinnerk van Bruinehsen
2014-09-23 14:42 ` [gentoo-user] " James
2014-09-23 16:52 ` [gentoo-user] James
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=542176B9.8080100@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-user@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