build: deal with newer glibc vs. FORTIFY_SOURCE
commit390d259efe8e1c7e4b6babb4738fef7427416857
authorEric Blake <eblake@redhat.com>
Tue, 26 Jun 2012 04:03:04 +0000 (25 22:03 -0600)
committerGary V. Vaughan <gary@gnu.org>
Wed, 18 Sep 2013 13:53:26 +0000 (18 20:53 +0700)
treea1e7140046f0a8b90b7bb62f2d465e8d82602f09
parentdeda5d4549291f15579b9c8ae4f9b1f862bc73bb
build: deal with newer glibc vs. FORTIFY_SOURCE

Recent glibc (for whatever stupid reason) decided to issue a #warning
when FORTIFY_SOURCE is requested but not possible, due to compilation
without optimization.  But when debugging sources, we don't want our
use of -Werror to kill compilation just because glibc wants to be
chatty; when debugging, we don't care about source fortification.
* configure.ac (FORTIFY_SOURCE): Make conditional on optimization.

Signed-off-by: Eric Blake <eblake@redhat.com>
configure.ac