From: Kerin Millar <kerframil@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] GCC4 (again...)
Date: Thu, 25 Jun 2009 14:39:42 +0100 [thread overview]
Message-ID: <279fbba40906250639g528656e7yc86bcae0ae9f501@mail.gmail.com> (raw)
In-Reply-To: <200906251518.28243.meyerm@fs.tum.de>
2009/6/25 Marcel Meyer <meyerm@fs.tum.de>:
> Hi,
>
> Am Donnerstag, 25. Juni 2009 schrieb Marcel Kummerow:
>> 2009/6/25 Ed W <lists@wildgooses.com>
>>
>> > [..] hardened GCC4
>> >
>> > Anyone able to provide such a summary please?
>>
>> http://forums.gentoo.org/viewtopic-t-705939.html
>
> what happens in the future when this overlay will no longer be provided?
If you're just looking for PIE support, you don't need any overlays.
Just unmask gcc-4.3.3-r2:
echo "=sys-devel/gcc-4.3.3-r2" >> /etc/portage/package.keywords
Upon installing/upgrading the ebuild in question, you'll find that a
set of hardened specs are provided:
[1] x86_64-pc-linux-gnu-4.3.3 *
[2] x86_64-pc-linux-gnu-4.3.3-hardenednopie
[3] x86_64-pc-linux-gnu-4.3.3-vanilla
If you're installing a system from scratch then, in my opinion, it is
a lot easier to rebuild a system seeded with a recent (vanilla)
autobuild stage than it is to use the hardened stages (which are still
based on gcc-3.4.6-r2 and usually stale in other respects).
Cheers,
--Kerin
next prev parent reply other threads:[~2009-06-25 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 11:02 [gentoo-hardened] GCC4 (again...) Ed W
2009-06-25 11:19 ` Marcel Kummerow
2009-06-25 13:18 ` Marcel Meyer
2009-06-25 13:39 ` Kerin Millar [this message]
2009-06-25 18:58 ` klondike
2009-06-26 1:11 ` Ed W
2009-06-26 1:43 ` Kerin Millar
2009-06-26 1:48 ` Kerin Millar
2009-06-26 7:08 ` klondike
2009-06-26 9:51 ` Ed W
2009-06-26 12:36 ` klondike
2009-06-26 14:39 ` atoth
2009-06-26 15:09 ` Magnus Grenberg
2009-06-26 5:00 ` atoth
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=279fbba40906250639g528656e7yc86bcae0ae9f501@mail.gmail.com \
--to=kerframil@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