On Tue, Jun 17, 2014 at 6:01 PM, Barry Schwartz <chemoelect...@chemoelectric.org> wrote: > Rich Freeman <ri...@gentoo.org> skribis: >> Usually use flags that are discouraged are intended mainly to solve >> limitations in how we express dependencies/etc. It isn't that we >> don't want users to use them, but more that in the future we might >> change how they work and they could go away, causing trouble for those >> who depend on them. Think of them as unintentionally-exposed private >> interfaces. > > My view on this current problem is that, given -fno-stack-protector in > the make.conf works nearly everywhere, there isn’t a problem as far as > building the OS is concerned. As for a ‘user compiler’, this seems not > to be a serious change, either. > > (An example of actually making life harder for a user are the > default-settings changes in Debian’s GNU linker. They make it harder > than with stock GNU to construct dynamic plugins.) >
As this topic is on-going, let my ask about -fno-stack-protector. I haven't messed with my build flags in literally years, and certainly not since I built this machine in 2010 where I only use CFLAGS="-O2 -march=native -pipe" . WRT to -fno-stack-protector does enabling a flag like that in make.conf then trigger a requirement to rebuild everything (emerge -e @world) or can one turn it on and just update the machine package-by-package over time? - Mark
