[Bug target/57753] FSF gcc bootstrap needs to use xcrun to bootstrap post-darwin12

[iains at gcc dot gnu.org]

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

Iain Sandoe  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #5 from Iain Sandoe  ---
closing this as a dup of 87243 (we now handle SDKROOT, and any other issues can
be picked up there)

*** This bug has been marked as a duplicate of bug 87243 ***

[Bug target/57753] FSF gcc bootstrap needs to use xcrun to bootstrap post-darwin12

[howarth at nitro dot med.uc.edu]

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

--- Comment #4 from Jack Howarth  ---
Actually, FSF gcc doesn't know about the SDKROOT path that xcrun sets. A change
similar to…

http://permalink.gmane.org/gmane.comp.compilers.clang.scm/56103

needs to be implemented on darwin so that FSF checks for the SDKROOT
environmental and uses it to find usr/include.

[Bug target/57753] FSF gcc bootstrap needs to use xcrun to bootstrap post-darwin12

[mikestump at comcast dot net]

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

--- Comment #3 from Mike Stump  ---
These should go in config/*darwin* I think.

[Bug target/57753] FSF gcc bootstrap needs to use xcrun to bootstrap post-darwin12

[howarth at nitro dot med.uc.edu]

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

--- Comment #2 from Jack Howarth  ---
Okay, the bootstrap without headers outside of the SDK can be simplified on
darwin to…

./configure -with-native-system-header-dir=`xcrun --show-sdk-path`/usr/include
CXX_FOR_BUILD="xcrun g++" CC_FOR_BUILD="xcrun gcc" CXXFLAGS="-O2 -g -iframework
`xcrun --show-sdk-path`/System/Library/Frameworks"

[Bug target/57753] FSF gcc bootstrap needs to use xcrun to bootstrap post-darwin12

[howarth at nitro dot med.uc.edu]

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

--- Comment #1 from Jack Howarth  ---
I should also note that removal of SDK from / isn't as bad as it sounds. In
general, most builds can puzzle out the location of the necessary headers.
However, FSF gcc is a complex build (especially regarding the fix includes
step) and in the absence of using xrcun, something like...

darwinvers=`sw_vers -productVersion | cut -d. -f1-2`
if [[ $darwinvers > 10.8 ]]; then
   if [ -d /Library/Developer/CommandLineTools ]; then
 configure CPPFLAGS="-O2 -g -isysroot `xcode-select
--print-path`/SDKs/MacOSX$darwinvers.sdk"
--with-native-system-header-dir=`xcode-select
--print-path`/SDKs/MacOSX$darwinvers.sdk/usr/include CXXFLAGS="-O2 -g
-iframework `xcode-select
--print-path`/SDKs/MacOSX$darwinvers.sdk/System/Library/Frameworks"
   else
 configure CPPFLAGS="-O2 -g -isysroot `xcode-select
--print-path`/Platforms/MacOSX.platform/Developer/SDKs/MacOSX$darwinvers.sdk"
--with-native-system-header-dir=`xcode-select
--print-path`/Platforms/MacOSX.platform/Developer/SDKs/MacOSX$darwinvers.sdk/usr/include
CXXFLAGS="-O2 -g -iframework `xcode-select
--print-path`/Platforms/MacOSX.platform/Developer/SDKs/MacOSX$darwinvers.sdk/System/Library/Frameworks"
   fi
 else 
   configure
 fi

has to be used. Note that using xrcun eliminates the need for end-user to
define where the SDK resides (i.e. in Xcode.app or Command Line Tools) as well
as avoiding the need to define which exact SDK release to use.