| 1 |
On Tue, Jun 17, 2014 at 6:44 PM, Barry Schwartz |
| 2 |
<chemoelectric@×××××××××××××.org> wrote: |
| 3 |
> Mark Knecht <markknecht@×××××.com> skribis: |
| 4 |
>> As this topic is on-going, let my ask about -fno-stack-protector. I |
| 5 |
>> haven't messed with my build flags in literally years, and certainly |
| 6 |
>> not since I built this machine in 2010 where I only use CFLAGS="-O2 |
| 7 |
>> -march=native -pipe" . WRT to -fno-stack-protector does enabling a |
| 8 |
>> flag like that in make.conf then trigger a requirement to rebuild |
| 9 |
>> everything (emerge -e @world) or can one turn it on and just update |
| 10 |
>> the machine package-by-package over time? |
| 11 |
> |
| 12 |
> If you _do not_ enable -fno-stack-protector you will get packages |
| 13 |
> updated over time, once you start using 4.8.3+ as your system |
| 14 |
> compiler. Enabling -fno-stack-protector is the way to keep things the |
| 15 |
> same. |
| 16 |
> |
| 17 |
Thanks for the clarifications Barry. |
| 18 |
Cheers, |
| 19 |
Mark |
Archives