public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50342] gcc/configure fails on Mac OS X Lion/Xcode 4.1 with recent GCCs
Date: Mon, 07 May 2012 23:09:00 -0000	[thread overview]
Message-ID: <bug-50342-4-ZDF6X57EYu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50342-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50342

--- Comment #9 from simon at pushface dot org 2012-05-07 21:13:48 UTC ---
(In reply to comment #8)

>   $srcdir/configure CC="gcc -D_FORTIFY_SOURCE=0”

Unfortunately doing this means that “gcc -v” with the built compiler contains
the ‘CC="gcc -D_FORTIFY_SOURCE=0”’ text in the Configured with: line, which
confuses gprconfig (part of AdaCore’s gprbuild tool). So the way I’ve adopted
for 4.7.0 is to start by

$ export CC="gcc -D_FORTIFY_SOURCE=0”
$ $srcdir/configure ...
$ make


  parent reply	other threads:[~2012-05-07 21:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09 13:51 [Bug bootstrap/50342] New: gcc/configure fails on Mac OS X Lion/Xcode 4.1 if building Ada simon at pushface dot org
2011-09-09 14:39 ` [Bug bootstrap/50342] " howarth at nitro dot med.uc.edu
2011-09-09 15:21 ` [Bug bootstrap/50342] gcc/configure fails on Mac OS X Lion/Xcode 4.1 with recent GCCs ebotcazou at gcc dot gnu.org
2011-09-09 16:31 ` howarth at nitro dot med.uc.edu
2011-09-09 18:38 ` ebotcazou at gcc dot gnu.org
2011-09-09 18:50 ` simon at pushface dot org
2011-09-09 18:56 ` simon at pushface dot org
2011-09-09 19:07 ` ebotcazou at gcc dot gnu.org
2011-09-09 20:51 ` simon at pushface dot org
2012-05-07 23:09 ` simon at pushface dot org [this message]
2012-05-08  2:14 ` mrs at gcc dot gnu.org
2012-05-08 20:48 ` simon at pushface dot org
2013-01-14 19:36 ` fago at earthlink dot net
2013-01-14 21:59 ` howarth at nitro dot med.uc.edu
2013-01-31 20:35 ` simon at pushface dot org
2013-01-31 21:00 ` howarth at nitro dot med.uc.edu
2013-12-21 23:12 ` dominiq at lps dot ens.fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-50342-4-ZDF6X57EYu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).