GNU bug report logs -
#12714
[PATCH] build: do not redefine _FORTIFY_SOURCE
Previous Next
Reported by: Mike Frysinger <vapier <at> gentoo.org>
Date: Tue, 23 Oct 2012 19:23:01 UTC
Severity: normal
Tags: patch
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On 10/23/2012 01:50 PM, Mike Frysinger wrote:
> On Tuesday 23 October 2012 15:26:14 Jim Meyering wrote:
>> Mike Frysinger wrote:
>>> If the active compiler or flags have already defined _FORTIFY_SOURCE,
>>> don't go overriding that. Otherwise we get a lot of spew about the
>>> flag being redefined.
>>>
>>> * configure.ac (FORTIFY_SOURCE): Check if _FORTIFY_SOURCE is defined.
>>>
>>> - #if defined __OPTIMIZE__ && __OPTIMIZE__
>>> + #if !defined _FORTIFY_SOURCE && defined __OPTIMIZE__ && __OPTIMIZE__
Coreutils copied this line from libvirt, and I know that other packages
have also copied this line. You will probably have several bug reports
to file, as you track down where this has spread.
I really dislike what glibc did to us by issuing a warning about an
ignored macro.
--
Eric Blake eblake <at> redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[signature.asc (application/pgp-signature, attachment)]
This bug report was last modified 12 years and 216 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.