move to high performance computer

Rosetta is using dynamically linked libraries (wikipedia that).  The short version is, you can’t move the executable from one machine to another, you need to recompile.

You can use a statically linked library with “extras=static” on your scons command line (so, scons.py -j# mode=release extras=static).  This produces much larger binaries that have most or all of their links internally and thus can be moved from computer to computer.  You can still only do this on matching architectures – you can’t compile on a mac and move to linux – but within similar linux distributions on similar hardware it is likely to work.

You can also just compile on the server resource, of course.

Note that when you switch to using a static compilation, the name of the executable you need to use changes. It’s no longer ~/rosetta/main/source/bin/antibody_H3.linuxclangrelease  it’s ~/rosetta/main/source/bin/antibody_H3.static.linuxclangrelease  If you’re using the name without the static, you may still be using the dynamically linked version.

The other thing you can try is to use the LD_LIBRARY_PATH environment variable to include the location of the library file. That is, you can do a `find ~/rosetta/main/source/build/  –name libcppdb.so`to find the appropriate directory, and then add the directory it’s in to your LD_LIBRARY_PATH environment variable. — I often do this when I’m running on a cluster. My cluster submission scripts have `export LD_LIBRARY_PATH=…` entries in them to set it prior to running Rosetta.