basile wrote:
> Yesterday I tried compiling gcc-4.3.2-r3 on a stock gentoo hardened
> uclibc system (uclibc-0.9.28.3-r7) and hit all the bugs I remembered
> hitting when I was helping Magnus with testing gcc-4* on uclibc. (Like
> the fenv.h issue).
>
> The best success I've had is using the toolchain from the hardened-dev
> overlay.  This includes upgrading both gcc and uclibc: gcc-4.4.1-r2,
> uclibc-0.9.30.1-r1, binutils-2.18-r3.  I can emerge -e world with only
> two issue, sandbox and python.  Take a look at bug 275094 for some clues
> on how to deal with python.  I haven't really tackled sandbox yet.
>
>   

Hi, Sandbox is fixed with sandbox-2.1 - the issue is/was a dodgy grep 
which then leads to some incorrect syntax in the config file - only 
fixed in 2.1
http://bugs.gentoo.org/show_bug.cgi?id=275725

However, I have had problems with sandbox violations using sandbox-2.1 
(e2fsprogs for example), so I reverted to 1.6-r3 and patched that up instead

I couldn't see any resolution for the Python compile issue other than 
commenting out the relevant includes as per comment 5:
http://bugs.gentoo.org/show_bug.cgi?id=275094

Apart from that it's looking pretty good (so far) with gcc-4.4.2-r1 + 
uclibc!

Thanks all

Ed W