This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/50342] gcc/configure fails on Mac OS X Lion/Xcode 4.1 with recent GCCs
- From: "simon at pushface dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 09 Sep 2011 19:50:05 +0000
- Subject: [Bug bootstrap/50342] gcc/configure fails on Mac OS X Lion/Xcode 4.1 with recent GCCs
- Auto-submitted: auto-generated
- References: <bug-50342-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50342
--- Comment #8 from simon at pushface dot org 2011-09-09 19:50:05 UTC ---
(In reply to comment #7)
> Try CC="gcc -D_FORTIFY_SOURCE=0" $srcdir/configure
Works. Works better if you say
$srcdir/configure CC="gcc -D_FORTIFY_SOURCE=0"
(then you don't need to say 'CC="gcc -D_FORTIFY_SOURCE=0" make').
> > On the other hand, we could reconsider -fkeep-inline-functions in the configure
> > scripts? The problem arises because the unsupported inlined builtin call is
> > (effectively) in <string.h>, so we don't need to actually call it.
>
> On Darwin, possibly, but otherwise I don't see any good reason to do that.
I suppose it might happen if say Red Hat decided to add builtins to their
system compiler/includes. But I agree, fairly unlikely. Also, I see you went
through a lot of pain in PR bootstrap/18058 putting -fkeep-inline-functions
into configure!