public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] GCC4 (again...)
Date: Fri, 26 Jun 2009 10:51:23 +0100	[thread overview]
Message-ID: <4A449A1B.5080002@wildgooses.com> (raw)
In-Reply-To: <fweka3l1vxn80cnpy9UYAxe124vaj_firegpg@mail.gmail.com>

klondike wrote:
>
>> Apologies for replying to my own post, but I just realised that you
>> were posing the question in the context of klondike's blog post. I do
>> not know what the status of SSP is in the overlays and/or experimental
>> toolchains so I'll bow out and leave it to one of the toolchain gurus
>> to provide a credible response. My answer applies to the gcc ebuild in
>> the mainline tree.
> Although I may be wrong, AFAIK SSP works nice with almost anything 
> except libstdc++, also packages which need it to be disabled (ie 
> thunderbird) usually do it without a problem of after pattching a bit 
> the ebuild. Anyway, I think the best one to answer is Zorry or Xake as 
> they maintain it.

So the Xake overlay is GCC 4.3.2 with the GCC 4 SSP enabled?

My limited understanding is that the GCC 4 (new) SSP implementation 
should be relatively benign and supported already by a modern toolchain 
with no further patches?  I would naively assume that since Redhat (and 
others) seem to be building their distros with it turned on that most 
packages would already be largely patched upstream to cope with it?  
(certainly I am more interested in server packages than desktop packages)

> Anyway, at least on the overlay uclibc is still not supported :( 
> http://github.com/Xake/toolchain-overlay/blob/54581c25b74be5a5dc3d8c1de61dba55db7c639f/README 
>

Does Xake hang out here?  Curious as to what the issues will be found in 
uclibc.  I'm not specially tied to uclibc, just that it seems to work 
nicely so far and I'm not desperately tight on drive space...

Ed W



  reply	other threads:[~2009-06-26  9:51 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
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 [this message]
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=4A449A1B.5080002@wildgooses.com \
    --to=lists@wildgooses.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