On Sun, Mar 23, 2014 at 04:21:46PM +0100, Simon Ruderich wrote: > 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.
I don't think that's posible (the "waf --help" output doesn't show anything
relevant), not without patching waf anyway. It'd be probably easier to make
blhc support this kind of output. But I'm not a waf expert so I may be wrong.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
