public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57792] toplevel configure should enable "--with-sysroot="`xcrun --show-sdk-path`"" for darwin13 and later
Date: Wed, 05 Nov 2014 13:21:00 -0000	[thread overview]
Message-ID: <bug-57792-4-19lDnK80o9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57792-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57792

--- Comment #13 from howarth at bromo dot med.uc.edu ---
Yes, I am pretty sure Apple has abandoned this for good. They only attempted
the change because it was assumed to be completely transparent as the compiler
looks in /usr/include by default. It wasn't appreciated that this would
cause...

radr://14320107 "/usr/bin/python reports back include directories that are
unpopulated"

where removal of /usr/include caused the system Python.h to point to an
unpopulated header directory in INCLUDEPY. While I provided them with a patch
to sysconfig.py to solve this, there is no stomach at Apple for pushing such
changes upstream as other packages like perl that hardcode compiler options
will need to be modified as well.
    While we could add this change to FSF gcc, I don't think we want to
encourage users not to install the system headers in /usr/include via the
Command Line Tools of Xcode as there are other configure scripts out there
which will also need to be patched to find /usr/include with `xcrun
--show-sdk-path`.
    If we made any change, I would rather it be a check in FSF gcc's configure
for the presence of /usr/include on darwin which provided the appropriate error
message to the user that the Command Line Tools needs to be installed.


  parent reply	other threads:[~2014-11-05 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-57792-4@http.gcc.gnu.org/bugzilla/>
2013-07-04 15:21 ` [Bug target/57792] fixincludes doesn't honor the use of --with-sysroot during bootstrap howarth at nitro dot med.uc.edu
2013-07-04 16:25 ` bkorb at gnu dot org
2013-07-04 17:27 ` howarth at nitro dot med.uc.edu
2013-07-04 23:35 ` [Bug target/57792] toplevel configure should enable "--with-sysroot="`xcrun --show-sdk-path`"" for darwin13 and later howarth at nitro dot med.uc.edu
2013-07-05  2:27 ` howarth at nitro dot med.uc.edu
2013-07-10 21:32 ` mrs at gcc dot gnu.org
2014-11-03 22:58 ` htl10 at users dot sourceforge.net
2014-11-04 20:00 ` howarth at bromo dot med.uc.edu
2014-11-04 20:01 ` howarth at bromo dot med.uc.edu
2014-11-05  5:40 ` htl10 at users dot sourceforge.net
2014-11-05 13:21 ` howarth at bromo dot med.uc.edu [this message]
2014-11-06 17:52 ` htl10 at users dot sourceforge.net
2014-11-06 18:02 ` mrs at gcc dot gnu.org
2014-11-06 18:38 ` iains at gcc dot gnu.org
2014-11-06 18:44 ` howarth at bromo dot med.uc.edu
2014-11-07  0:41 ` htl10 at users dot sourceforge.net
2014-11-07  2:17 ` howarth at bromo dot med.uc.edu
2014-11-08 14:53 ` iains at gcc dot gnu.org

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-57792-4-19lDnK80o9@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).