| 1 |
basile wrote: |
| 2 |
> Yesterday I tried compiling gcc-4.3.2-r3 on a stock gentoo hardened |
| 3 |
> uclibc system (uclibc-0.9.28.3-r7) and hit all the bugs I remembered |
| 4 |
> hitting when I was helping Magnus with testing gcc-4* on uclibc. (Like |
| 5 |
> the fenv.h issue). |
| 6 |
> |
| 7 |
> The best success I've had is using the toolchain from the hardened-dev |
| 8 |
> overlay. This includes upgrading both gcc and uclibc: gcc-4.4.1-r2, |
| 9 |
> uclibc-0.9.30.1-r1, binutils-2.18-r3. I can emerge -e world with only |
| 10 |
> two issue, sandbox and python. Take a look at bug 275094 for some clues |
| 11 |
> on how to deal with python. I haven't really tackled sandbox yet. |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
Hi, Sandbox is fixed with sandbox-2.1 - the issue is/was a dodgy grep |
| 16 |
which then leads to some incorrect syntax in the config file - only |
| 17 |
fixed in 2.1 |
| 18 |
http://bugs.gentoo.org/show_bug.cgi?id=275725 |
| 19 |
|
| 20 |
However, I have had problems with sandbox violations using sandbox-2.1 |
| 21 |
(e2fsprogs for example), so I reverted to 1.6-r3 and patched that up instead |
| 22 |
|
| 23 |
I couldn't see any resolution for the Python compile issue other than |
| 24 |
commenting out the relevant includes as per comment 5: |
| 25 |
http://bugs.gentoo.org/show_bug.cgi?id=275094 |
| 26 |
|
| 27 |
Apart from that it's looking pretty good (so far) with gcc-4.4.2-r1 + |
| 28 |
uclibc! |
| 29 |
|
| 30 |
Thanks all |
| 31 |
|
| 32 |
Ed W |
Archives