Re: [PATCH] Add -D_FORTIFY_SOURCE=2 to CFLAGS if possible.

2017-02-15 Thread Mark Wielaard
On Tue, 2017-02-14 at 21:58 -0500, Mike Frysinger wrote: > On 09 Feb 2017 21:13, Mark Wielaard wrote: > > +# See if we can add -D_FORTIFY_SOURCE=2. Don't do it if it is already > > +# (differently) defined or if it generates warnings/errors because we > > +# don't use the right optimisation level (

Re: [PATCH] Add -D_FORTIFY_SOURCE=2 to CFLAGS if possible.

2017-02-14 Thread Mike Frysinger
On 09 Feb 2017 21:13, Mark Wielaard wrote: > +# See if we can add -D_FORTIFY_SOURCE=2. Don't do it if it is already > +# (differently) defined or if it generates warnings/errors because we > +# don't use the right optimisation level (string.h will warn about that). > +AC_MSG_CHECKING([whether to ad

Re: [PATCH] Add -D_FORTIFY_SOURCE=2 to CFLAGS if possible.

2017-02-14 Thread Mark Wielaard
On Thu, 2017-02-09 at 21:13 +0100, Mark Wielaard wrote: > Some distros now add -D_FORTIFY_SOURCE=2 by default and we have missed > some issues in the past caught by it. Add it to CFLAGS if possible. > The configure check will make sure that it doesn't conflict with any > other CFLAGS already define

[PATCH] Add -D_FORTIFY_SOURCE=2 to CFLAGS if possible.

2017-02-09 Thread Mark Wielaard
Some distros now add -D_FORTIFY_SOURCE=2 by default and we have missed some issues in the past caught by it. Add it to CFLAGS if possible. The configure check will make sure that it doesn't conflict with any other CFLAGS already defined. Signed-off-by: Mark Wielaard --- ChangeLog| 4 c