I’m not sure why we’re suddenly talking about v5.34.32. The version I’m trying to compile is the latest ROOT6 version, which gives the same error.
gbesjes@imac-besjes:~ $ source bin/root-6.02.12/bin/thisroot.sh
gbesjes@imac-besjes:~ $ echo $LD_LIBRARY_PATH
/Users/gbesjes/bin/root-6.02.12/lib
The paths are OK:
/Users/gbesjes/bin/root-6.02.12/lib/libPyROOT.so:
@rpath/libPyROOT.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libTree.so (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.10)
@rpath/libRIO.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libCore.so (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1225.1.1)
Setting $DYLD_LIBRARY_PATH to $LD_LIBRARY_PATH does not solve the issue.
A different machine with a ROOT6 installation on OS X 10.10 has rather similar output:
gbesjes@supermac:~ $ otool -L $ROOTSYS/lib/libPyROOT.so
/cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase/x86_64-MacOS/root/6.02.12-x86_64-mac1010-clang61-opt/lib/libPyROOT.so:
@rpath/libPyROOT.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libRIO.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libTree.so (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.6)
@rpath/libCore.so (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
This seems to me the same as above. What I ran is the following:
This solves the issue. The output of otool is now:
gbesjes@imac-besjes:~ $ otool -L $ROOTSYS/lib/libPyROOT.so
/Users/gbesjes/bin/root-6.02.12-rpath-hack/lib/libPyROOT.so:
@rpath/libPyROOT.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libTree.so (compatibility version 0.0.0, current version 0.0.0)
/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.10)
@rpath/libRIO.so (compatibility version 0.0.0, current version 0.0.0)
@rpath/libCore.so (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1225.1.1)
Which, as you can see, has not changed. My original compilation command was
cmake -DCMAKE_INSTALL_PREFIX=$HOME/bin/root-6.02.12 -DCMAKE_BUILD_TYPE=Release -Dall=ON ../root-6.02.12
make -j6
make install
Presumably, something in the cmake (or autoconf, judging from the other issues reported) goes wrong on 10.11 w.r.t. 10.10. It would be great if it could be fixed - I don’t think setting rpath by hand makes the binary very portable!