| 1 |
On Monday 01 February 2010 22:37:59 Gordon Malm wrote: |
| 2 |
> You might want to try building a |
| 3 |
> non-hardened compiler and use it as an intermediate step to building the |
| 4 |
> hardened gcc-4.3.4 compiler. |
| 5 |
I was considering that, but how exactly should I do? Like [1] shows? |
| 6 |
|
| 7 |
That is: given >=sys-devel/binutils-2.17: |
| 8 |
|
| 9 |
gcc-config -l |
| 10 |
gcc-config <current gcc>-vanilla |
| 11 |
source /etc/profile |
| 12 |
|
| 13 |
USE="-hardened" emerge --oneshot sys-libs/glibc |
| 14 |
USE="-hardened" emerge --oneshot sys-devel/gcc |
| 15 |
|
| 16 |
gcc-config -l |
| 17 |
gcc-config <new gcc>-hardened |
| 18 |
source /etc/profile |
| 19 |
|
| 20 |
emerge --oneshot sys-libs/glibc |
| 21 |
emerge --oneshot sys-devel/gcc |
| 22 |
|
| 23 |
? |
| 24 |
|
| 25 |
|
| 26 |
If I'd proceed with emerge -avDuN system world (btw, is that the same as for |
| 27 |
"system" and "world" separately in that order?), can the old binaries on my |
| 28 |
system have any really probable conflicts for the new glibc and new-gcc-build |
| 29 |
other parts? After I'd compile and install a non-hardened glibc, wouldn't I |
| 30 |
break some hardened binaries?! |
| 31 |
|
| 32 |
I'd like to find answers to those questions first... |
| 33 |
|
| 34 |
|
| 35 |
[1] http://www.gentoo.org/proj/en/hardened/toolchain-upgrade-guide.xml |
Archives