On Wed, Mar 12, 2014 at 04:49:31PM +0100, Alessandro Ghedini wrote: > Pushed to git, thanks! Note that we already pass "-v" to waf, so "V := 1" > isn't > needed (and it doesn't work with waf anyway).
Hello,
Thanks for fixing it so quickly.
Would it be possible to patch/modify the build system to generate
output parseable by blhc to verify all hardening flags are
applied correctly?
At the moment it looks like this:
15:39:24 runner ['/usr/bin/cc', '-D_FORTIFY_SOURCE=2', '-g', '-O2',
If this could get changed to:
15:39:24 runner /usr/bin/cc -D_FORTIFY_SOURCE=2 -g -O2 ..
then blhc (used by the buildd log scanner [1]) could verify the
compiler commands.
Regards
Simon
[1]: http://qa.debian.org/bls/index.html
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: Digital signature
