| 1 |
Am Dienstag, 10. Oktober 2017, 04:10:13 CEST schrieb Duncan: |
| 2 |
|
| 3 |
> One thing isn't clear here. Is this sequence necessary due to the |
| 4 |
> profile switch itself, because the /profile/ enables PIE by default, or |
| 5 |
> is it gcc-6.4+ that enables PIE, and the profile simply forces the PIE |
| 6 |
> default by forcing gcc-6.4+? |
| 7 |
|
| 8 |
Switching the profile changes the settings for building gcc (it switches a use- |
| 9 |
flag from forced-off to forced-on). A gcc-6 built with the 17.0 profiles will |
| 10 |
produce PIE executables by default, a gcc-6 built with the 13.0 profiles will |
| 11 |
not. |
| 12 |
|
| 13 |
I've added this paragraph: |
| 14 |
# Switching the profile modifies the settings of GCC 6 to generate |
| 15 |
# PIE executables by default; thus, you need to do the rebuilds |
| 16 |
# even if you already used GCC 6 beforehand. |
| 17 |
|
| 18 |
> The answer makes a big difference to those already on gcc-6.4+ and who |
| 19 |
> presumably already did an empty-tree rebuild of @world when upgrading to |
| 20 |
> it, |
| 21 |
|
| 22 |
That's really not necessary anymore. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Andreas K. Hüttel |
| 27 |
dilfridge@g.o |
| 28 |
Gentoo Linux developer (council, perl, libreoffice) |
Archives