/Projects/tl% sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer /Projects/tl% xcrun -f lipo /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo /Projects/tl% sudo xcode-select --switch /Applications/Xcode4.app/Contents/Developer /Projects/tl% xcrun -f lipo /usr/bin/lipo /Projects/tl% sudo xcode-select --reset /Projects/tl% xcrun -f lipo /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo
On Oct 24, 2013, at 3:09 PM, Jim Laskey (Oracle) <james.las...@oracle.com> wrote: > > On Oct 24, 2013, at 2:53 PM, David DeHaven <david.deha...@oracle.com> wrote: > >> >>> I managed to build OpenJDK on Mavericks using the Xcode4 tool chain, with >>> one minor glitch (Bob, installing Quartz X11 addresses X11 issues.) >>> >>> Before installing Mavericks, I renamed Xcode.app to Xcode4.app. >>> >>> I then installed Mavericks and sundry updates (Xcode5, iTunes, iWorks, >>> iLife, ...) >>> >>> After checking out tl, I configured with >>> >>> sh ./configure >>> --with-tools-dir=/Applications/Xcode4.app/Contents/Developer/usr/bin >> >> You can also install the Xcode 4 command line tools and run "sudo >> xcode-select --switch /Applications/Xcode4.app" then you shouldn't need the >> --with-tools-dir configure argument (I have both 4.6 and 5 installed). The >> Xcode 5 command line tools clobber the gcc symlinks, which is (IMHO) a bug >> in Apples CL tools installer... >> > > I tried that and the build scripts seemed to hang on "xcrun lipo" > >> >> I think ultimately we should investigate using xcrun to find the tools >> rather than relying on xcode-select. With that we could build without having >> the command line tools installed at all. The configure script should be able >> to do this, then use the same mechanism as --with-tools-dir to set the tool >> path. >> >> For example: >> $ xcrun -f clang >> /Applications/Xcode_4.6.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang >> >> -DrD- >> >
