I'm running a Mac 10.9 64Bit system, and I'm trying to build it against a homebrewed install of Python 2.7.6. I'm using the 2014wk05 rosetta bundle.
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Thread model: posix
There have been several issues along the way, which have been addressed in a different thread (https://www.rosettacommons.org/node/3608) but it seemed it would be more appropriate to move the discussion here.
I found that when using clang to compile PyRosetta, there were multiple points at which the compiler was expecting clang version 5.0 when the current version is 5.1 - specifically, it's looking for a bunch of lib files in build/src/pyrosetta/macos/10.9/64/x86/clang/5.0/default/ when the actual directory tree uses 5.1 instead of 5.0. To illustrate, here's the error that it returns when it tries to link libmini.dylib:
Linking mini lib...
cd /Users/juliaudell/Downloads/rosetta_2014wk05_bundle/main/source && cd build/src/pyrosetta/macos/10.9/64/x86/clang/5.0/default/ && gcc -dynamiclib -Xlinker -headerpad_max_install_names\
... [long list of .os files]
-lz -lstdc++ -o /Users/juliaudell/Downloads/rosetta_2014wk05_bundle/main/source/src/python/bindings/rosetta/libmini.dylib
it gives the error
/bin/sh: line 0: cd: build/src/pyrosetta/macos/10.9/64/x86/clang/5.0/default/: No such file or directory
Furthermore it looks like the clang version is hard coded in BuildBindings.py, line 684:
elif platform.release()[:2] == '13': lib_path = 'build/src/'+mode+'/macos/10.9/64/x86/clang/'; version_add_on = '5.0/default/'
lib_path = lib_path += version_add_on
Using -I/ and -L/ doesn't help things, and while I can include a flag for a different compiler, there doesn't appear to be a way to flag for the version.
Changing the version number in the version_add_on variable yields a whole slew of "symbols not found for architecture x86_64" errors, attached here.
Where do I go from here?