On Sun, Aug 10, 2014 at 02:04:18PM +0200, Matthias Klose wrote: > sorry if this is a duplicate, but according to > https://qa.debian.org/bls/packages/p/python2.7.html > > the build log checker warns even for a debug build with -O0 (or missing -O*) > and > missing -D_FORTIFY_SOURCE. I don't think that such debug builds should be > forced > to use -D_FORTIFY_SOURCE.
Hello Matthias, Thanks for the report. Should be fixed in Git commit ac2b8c [1]. However lines missing all -O* flags still report missing fortification as it was easier to implement and shouldn't be an issue in normal usage (if no -O* is used then most likely no $CFLAGS were passed to the compiler and it's a problem in the build system - also prevents false negatives). Regards Simon [1]: http://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=ac2b8ce3fb580510632eba88382555b22165e059 -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: Digital signature
