From: "Claes Gyllenswärd" <letharion@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] gcc-4.3.4 stabilized for a hardened profile?
Date: Sun, 18 Oct 2009 17:51:45 +0200 [thread overview]
Message-ID: <ffd1161b0910180851k2943fbe7ra1b6078feb90e861@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10910180842t3d34efd5h20af2a937d75bb1c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
I haven't seen any posts with problems.
I use x86 and haven't noticed any problems either, but I haven't used that
system much.
Check bugzilla.
Pasting the original announcement below.
2009/10/18 Grant <emailgrant@gmail.com>
> I've been stuck on gcc-3.4.6 on my hardened profile system (currently:
> hardened/linux/amd64/10.0) for a very long time. Now it looks like
> gcc-4.3.4 has been stabilized for hardened profiles. Has anyone
> tested it? This system is critical for me, so I've got to be careful.
>
> - Grant
>
>
Hello Hardened users, this is just a quick heads up. GCC 4.3.4 will be
going
stable on hardened profiles shortly. Unlike Hardened GCC 3.4.6, this
version
lacks default SSP building. However, FORTIFY_SOURCE=2
and -fno-strict-overflow are now enabled by default. Other Hardenedcompiler
features (ex. default relro, bind now & pic/pie building) remain enabled -
no
change from 3.4.6.
It is regretable this must be done before GCC4 is SSP-by-default enabled.
However, more and more packages require the newer GCC. The stable GCC on
Hardened has been GCC 3.4.6 for a long time, but this has become an
untenable
situation. GCC4 SSP-by-default works and will be added in a later revision
-
some GCC4+SSP bugs in grub and glibc also remain to be fixed.
Please follow '2. General Upgrade Instructions' in the 'Gentoo GCC Upgrade
Guide' [1] when upgrading from GCC 3.4.x to GCC 4.3.x. The upgrade should
be
relatively smooth, but if you run into upgrade troubles seek help via this
mailing list, bugs.gentoo.org, or irc.freenode.net, #gentoo-hardened.
[1] http://www.gentoo.org/doc/en/gcc-upgrading.xml
[-- Attachment #2: Type: text/html, Size: 2532 bytes --]
next prev parent reply other threads:[~2009-10-18 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 15:42 [gentoo-hardened] gcc-4.3.4 stabilized for a hardened profile? Grant
2009-10-18 15:51 ` Claes Gyllenswärd [this message]
2009-10-18 16:18 ` Ed W
2009-10-18 18:45 ` Michael Orlitzky
2009-10-27 18:53 ` Grant
2009-10-27 19:57 ` Michael Orlitzky
2009-10-27 20:55 ` klondike
2009-10-27 22:53 ` Pavel Labushev
2009-10-27 22:50 ` Pavel Labushev
2009-10-28 2:59 ` Mike Edenfield
2009-10-28 4:33 ` Michael Orlitzky
2009-10-29 21:55 ` Mike Edenfield
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=ffd1161b0910180851k2943fbe7ra1b6078feb90e861@mail.gmail.com \
--to=letharion@gmail.com \
--cc=gentoo-hardened@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