https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90834
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Iain Sandoe from comment #10) > (In reply to John Marshall from comment #9) > > This has an unfortunate side-effect that the compiler looks in the > > non-existent /Library/.../MacOSX.sdk/usr/local/include instead of > > /usr/local/include [2]. > > That's an irritation, indeed. > It's possible we could work around the /usr/include/local thing relatively > easily, one can add un-sysrooted paths (and also compiler-relative paths). Having said this, what does clang do? We probably want to avoid doing things too much differently, or people's build systems will behave in unexpected ways with GCC c.f. clang. on a regular Xcode installation what do you get for clang -xc /dev/null -fsyntax-only -v ?
