1 |
On 12/05/2017 02:45 PM, Michael Orlitzky wrote: |
2 |
> On 12/05/2017 03:26 PM, Corbin wrote: |
3 |
>> In "packages" that throw out the "CFLAGS / CXXFLAGS" values in the |
4 |
>> end-users "make.conf" and substitute their own ... how will that be handled? |
5 |
>> |
6 |
> The GCC ebuilds all use toolchain.eclass which is incomprehensible to |
7 |
> me, but it looks like the default behavior for gcc-6.x is to pass |
8 |
> "--enable-default-pie" and "--enable-default-ssp" to the build process |
9 |
> of GCC itself. That changes the default behavior of GCC to (as the names |
10 |
> say) enable PIE and SSP by default. |
11 |
> |
12 |
> Consequently, if a package ignores your CFLAGS, the PIE/SSP should still |
13 |
> take effect, because GCC does them by default. Only a package that adds |
14 |
> its own -no-pie flag (for example) would cause problems. |
15 |
> |
16 |
A Master Override ... in other words. |
17 |
|
18 |
Thank You. |
19 |
|
20 |
Corbin |