On Fri, Jun 13, 2014 at 9:22 AM, Jeroen Roovers <j...@gentoo.org> wrote: > The problem I see is that anyone who wants to switch to having > -fstack-protector enabled by default early will run into the glibc > problem (much as I did), when all the bug reports that point out the > problem have been closed as INVALID. A simple `strip-flags > -fstack-protector' in the appropriate (non-hardened?) cases should > prevent more duplicate bug reports, I guess.
++ If we know everybody is going to be on -fstack-protector in a few months just add the strip-flags statement to the ebuild and be done with it. Squabbling over whether those using the flag are bringing breakage upon themselves is like trying to hold back the sea. We should be encouraging people to add the flag and report bugs, and if a package doesn't work with it and doesn't strip it I think we should consider it a package bug now. Ten years ago when it was fairly unsupported the argument made more sense (you can't filter every little thing that can break a package). Rich
