https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57792
--- Comment #17 from howarth at bromo dot med.uc.edu --- (In reply to Hin-Tak Leung from comment #14) > (In reply to howarth from comment #13) > > > > 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. > > I don't think mandating Command Line Tools would be a good idea - I think in > that case you can have a reverse problem when your intention is to build > stuff for other people: you build x intended for others, you have > /usr/include but others don't, x made assumptions about the intended users > having the same stuff as yours, and it doesn't work on the intended user's > machine, or have mysterious errors. 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.
