RFR: [9] 8043340 & 8043591: [macosx] Build system issues

David DeHaven david.dehaven at oracle.com
Wed Jun 11 16:37:22 UTC 2014

>>> $ sudo xcode-select -switch /Applications/old/Xcode4.app
>>> $ make clean; sh ./configure; make images
>>> Broken! The current Xcode command line tools don't run gcc as gcc even if Xcode 4 is active
>>> Nothing we can do about this, anyone needing to use Xcode 4 will need to use --with-toolchain-path or --with-toolchain-type=clang (as below)
>>> Hudson/JPRT should not be affected unless they also have Xcode 5 installed
> I assume this is because xcodebuild --version will report 4 in this case as 4 is set to active, but command line tools in /usr/bin are not updated accordingly?

The stub tools seem to be hard wired to run clang, even if gcc really is there.

This is only one of several problems with Apple's command line tools at the moment. Another more annoying issue is when you run lipo from /usr/bin with Xcode 4 active it will deadlock.

> If --with-toolchain-path=<xcode4> work, perhaps we can set this based on version reported by xcodebuild?

I thought about that, but the workaround should be good enough for our purposes. The goal is for everyone to be able to build on Xcode 5 with clang anyways :)


More information about the build-dev mailing list