[arch-dev-public] Add -fstack-protector{-all} to default CFLAGS?

Allan McRae allan at archlinux.org
Wed May 12 04:57:27 EDT 2010

On 12/05/10 18:31, Thomas Bächler wrote:
> Am 12.05.2010 09:46, schrieb Allan McRae:
>> Honestly, if I wanted comments about gcc and busybox, the subject of
>> this email would have been something like "busybox build issues with
>> gcc-4.5".  And then I would have scolded myself for not using the bug
>> tracker.
>> Can I just have comments on the proposed CFLAGS?
> Okay, then you'll get a comment on that: Our toolchain is terribly
> broken as it is, let's break it further by adding more flags.

Terribly broken?  17% of our repo has been rebuilt since it moved to 
[core] and 1 package has been reported broken due to gcc. That is 0.07% 
of packages and even that has a workaround.  How terrible...

So, do I really have to wait until that is fixed before we can discuss 
_future_ changes?


More information about the arch-dev-public mailing list