> For a transition we can probably build everything with -fPIE but not > link with -pie. If we want that to happen fast, gcc-6 might do that and > gcc-7 add the -pie option.
I am not entirely convinced that a transition period of one gcc version
is enough for a smooth transition [1].
It might be better to go through a quick transition process that
requires a world rebuild. - In particular we already forced everyone on
~amd64 to play beta tester in this regard [2,3].
Anyway the current use flag situation is a mess and has to be cleaned
up asap.
So, dos anyone recall why USE=pie was masked for >gcc-6.2 for everyone
except amd64?
Related to that
- for which architectures shall we unmask the use flag?
- shall we use.force a certain behavior per profile, or keep the flag
unpinned?
After having thought about the issue for a bit I still want to propose
what we have already accidentally done - switch to USE=pie per default
for gcc-6.
Best,
Matthias
[1] Indeed *every* major linux distribution for which I have an lxc
container has -pie enabled. If we decide on some slow transition we
risk to be late to the party by quite a bit.
[2] Which is extremely unfortunate.
[3] The fallout I currently see due to enabled USE=pie is noticeably but
by no stretch crazy bad. After all, static linkage is rarely used
(with the exception of some languages).
signature.asc
Description: PGP signature
