]> git.ipfire.org Git - thirdparty/knot-resolver.git/commit
make: don't magically -D_FORTIFY_SOURCE=2
authorVladimír Čunát <vladimir.cunat@nic.cz>
Wed, 7 Mar 2018 09:40:25 +0000 (10:40 +0100)
committerVladimír Čunát <vladimir.cunat@nic.cz>
Mon, 19 Mar 2018 11:54:50 +0000 (12:54 +0100)
commitb15476ecbecb6893f8dd1c6c520e3e56262ad458
treeddbbb42f78a56b61f7ab7a7ba1c986317575a90a
parent343bf36ce8ad606a40d4d2bdfa271e475e0cdc23
make: don't magically -D_FORTIFY_SOURCE=2

This is just annoying for development.  You want -O0 or -Og,
and consequently you get lots of warnings that are difficult to disable.

I believe hardening options are more of a responsibility/choice of the
caller, typically distributions have some general policies and pass the
flags (almost) uniformly to all packages.  I can't see any part of kresd
being so specific to warrant explicit hardening.
NEWS
config.mk