From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] gcc-4.3.4 stabilized for a hardened profile?
Date: Wed, 28 Oct 2009 00:33:37 -0400 [thread overview]
Message-ID: <4AE7C9A1.4060200@orlitzky.com> (raw)
In-Reply-To: <4AE7B398.3070509@kutulu.org>
Mike Edenfield wrote:
> On 10/27/2009 6:50 PM, Pavel Labushev wrote:
>> Michael Orlitzky wrote:
>>
>>> using hardened for a desktop machine. A few packages, e.g.
>>
>>> * Mplayer
>>> * OpenOffice
>>
>> There wasn't a /single/ failure on x86 with these two for me, despite I
>> compiled it with 3.4.6/4.1.2/4.3.3 - all are hardened and allways with
>> SSP flags enabled in specs. So at least it worth a try before switching
>> to vanilla compilers.
>
> Both of these fail for me on hardened amd64, though my admittedly
> sketchy memory tells me both built fine when I was running hardened x86
> on the same hardware a few months back.
>
> The mplayer failure is the same one that's always caused problems for
> SSP -- running out of registers in parts of the assembly code. The OOo
> build fails on three separate steps for three seemingly unrelated
> reasons, none of which I have had time to chase down.
OpenOffice fails about an hour into compilation for me, so screw that.
All of my desktop machines are amd64 -- x86 users might have better
luck, especially now that 4.x is stable.
If you have any trouble during the 'emerge -ve world', please unleash a
fury upon bugzilla.
next prev parent reply other threads:[~2009-10-28 4:33 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
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 [this message]
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=4AE7C9A1.4060200@orlitzky.com \
--to=michael@orlitzky.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