From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "stack-protector-strong" option results in gcc error
Date: Tue, 23 Sep 2014 04:54:03 -0400 [thread overview]
Message-ID: <20140923085403.GA4540@waltdnes.org> (raw)
In-Reply-To: <CAJ1xhMVPaWUnam+ZPp-BBrw=sYSu_BXN_NxdmuMB8ON83o75tg@mail.gmail.com>
On Tue, Sep 23, 2014 at 09:16:42AM +0300, Alexander Kapshuk wrote
>
> Looks like support for '-fstack-protector-strong' was implemented in
> more recent versions of gcc. The the URL below for details:
>
> https://securityblog.redhat.com/tag/stack-protector/
Thanks for the explanation. The blog says...
> GCC 4.8.1 and the GCC version in Fedora 19 added another mode,
> -fstack-protector-strong, bringing the number of stack protector
> modes up to three.
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.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2014-09-23 8:54 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 [this message]
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
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=20140923085403.GA4540@waltdnes.org \
--to=waltdnes@waltdnes.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