I'd be inclined to agree, but along the way I had tried xcode-select --install, which has no effect, and gives the error that the command line tools were already installed. I read somewhere that installing the full xcode app is necessary (or does this just run some kind of update?)
On Wed, Jan 20, 2016 at 9:21 PM Isaiah Norton <[email protected]> wrote: > Probably outdated/mismatched XCode version leading to some error earlier > in the build. See: > https://github.com/JuliaLang/julia/issues/14593 > https://github.com/JuliaLang/julia/pull/14605 > > On Wed, Jan 20, 2016 at 7:59 PM, Jonathan Goldfarb <[email protected]> > wrote: > >> Not sure if this is the place for this kind of discussion, but here goes. >> Been building from source from master periodically and enjoying poking >> around in the source, but have run into an issue apparently due to the >> updated LLVM version, and am wondering if anyone else is having similar >> issues. After removing (I think) everything, including "brew rm --force >> $(brew deps --HEAD julia);", I tried the following: >> >> - brew install git gcc >> - clone julia repo to clean directory >> - Add >> >> BUILD_LLVM_CLANG=1 >> to Make.user as suggested by Clang.jl/Cxx.jl (removing this step does not >> apparently fix the build, but changes the error) >> >> - run make >> >> and have gotten the following: >> >> llvm[6]: Copying runtime library darwin/eprintf to build dir >> cp: >> /Users/jgoldfar/Public/julia/deps/build/llvm-3.7.1/build_Release/tools/clang/runtime/compiler-rt/clang_darwin/eprintf/libcompiler_rt.a: >> No such file or directory >> make[6]: *** >> [/Users/jgoldfar/Public/julia/deps/build/llvm-3.7.1/build_Release/Release/lib/clang/3.7.1/lib/darwin/libclang_rt.eprintf.a] >> Error 1 >> make[5]: *** [compiler-rt/.makeall] Error 2 >> make[4]: *** [all] Error 1 >> make[3]: *** [clang/.makeall] Error 2 >> make[2]: *** [all] Error 1 >> make[1]: *** >> [build/llvm-3.7.1/build_Release/Release/lib/libLLVMCodeGen.a] Error 2 >> make: *** [julia-deps] Error 2 >> >> Searching online suggests that this was an error with an older version of >> clang/LLVM, but it appears here again. >> >> Anybody else running into this? >> >> Regards, >> Max >> > > -- Regards, Max Goldfarb
