https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57792
--- Comment #18 from Hin-Tak Leung <htl10 at users dot sourceforge.net> --- (In reply to m...@gcc.gnu.org from comment #15) > Mandating commands line tools is fine. Would be nice if everything worked > flawlessly if no optional package had to be installed, but I'm pragmatic. The current behavior is definitely wrong: without command line tools and without --with-sysroot (i.e. just plain ./configure), ./configure returns success, but only fail to 'make' towards the end of stage1 when the build system tries to do the 'stage1-fixincludes' target. ./configure should either auto-add the --with-sysroot (as the reverted fix did), or abort with an appropriate message, like the requirement for gmp/mpfr/mpc. successful ./configure then failing part-way through make is bad. (In reply to howarth from comment #17) > You have to remember that Apple expects you to build everything from within > the Xcode projects while the Command Line Tools package exists to handle > building outside of that mechanism. The unfortunate fact is that far too > much software explicitly expects headers in /usr/include to avoid installing > the Command Line Tools. In the fink project, we get endless bug reports from > users who fail to install the Command Line Tools. Not really. Actually xcode 6.1 seem to ships all the command line tools. doing 'xcode-select --install' install a much older(?) command line tools plus headers in /usr/include. I don't know if Apple is going to keep that in-sync, but there might be a danger of the headers in /usr/include not really describing the system. Also, people who DIY are supposed to go through all the troubles... you still haven't addressed the issue of new gcc (+ xcode building it with) may generate stuff that have additional dependencies on /usr/include, if /usr/include is around, and therefore not suitable when one is building things for others.
