| 1 |
Andreas K. Huettel posted on Tue, 10 Oct 2017 21:02:32 +0200 as excerpted: |
| 2 |
|
| 3 |
> Am Dienstag, 10. Oktober 2017, 04:10:13 CEST schrieb Duncan: |
| 4 |
> |
| 5 |
>> One thing isn't clear here. Is this sequence necessary due to the |
| 6 |
>> profile switch itself, because the /profile/ enables PIE by default, or |
| 7 |
>> is it gcc-6.4+ that enables PIE, and the profile simply forces the PIE |
| 8 |
>> default by forcing gcc-6.4+? |
| 9 |
> |
| 10 |
> Switching the profile changes the settings for building gcc (it switches |
| 11 |
> a use-flag from forced-off to forced-on). A gcc-6 built with the 17.0 |
| 12 |
> profiles will produce PIE executables by default, a gcc-6 built with |
| 13 |
> the 13.0 profiles will not. |
| 14 |
> |
| 15 |
> I've added this paragraph: |
| 16 |
> # Switching the profile modifies the settings of GCC 6 to generate |
| 17 |
> # PIE executables by default; thus, you need to do the rebuilds |
| 18 |
> # even if you already used GCC 6 beforehand. |
| 19 |
|
| 20 |
Thanks. Much clearer now. =:^) |
| 21 |
|
| 22 |
(And I'll have some rebuilding to do.) |
| 23 |
|
| 24 |
-- |
| 25 |
Duncan - List replies preferred. No HTML msgs. |
| 26 |
"Every nonfree program has a lord, a master -- |
| 27 |
and if you use the program, he is your master." Richard Stallman |
Archives