Hmm, I'm pretty sure my xhpl binary is/was dynamic linked. Here is my env: LD_LIBRARY_PATH=/share/apps/openmpi-1.10-intel-x86_64/lib:/share/apps/Intel/composer_xe_2015.2.164/compiler/lib/intel64:/share/apps/Intel/composer_xe_2015.2.164/mkl/lib/intel64:/opt/python/lib
The binary fails without a symlink to libmpi.so.1. So I'm not sure if you're saying yes create a symlink or yes rebuild the binary. Or it should work, and no symlink should be necessary. >Jeff will undoubtedly start typing before he reads my response, so I'll >spare you from reading all the ugly details twice :-) >There was an unintentional ABI break in the 1.8 series that necessitated a >version numbering change to libmpi. It involves the code that handles the >connection between a process and its local daemon. If you hard link (e.g., >static build) your app against a pre-1.8.5 lib and then run it against a >1.8.5+ version of mpirun, it will fail. >However, if you dynamically link, everything should be fine so long as the >app's LD_LIBRARY_PATH points to the 1.8.5+ shared libs. >Ralph
