Re: [OMPI users] Problems in compiling a code with dynamic linking

[Thomas Jahns]

Hello,

On 03/24/2016 03:22 AM, Gilles Gouaillardet wrote:

it seems /opt/intel/composer_xe_2013_sp1/bin/compilervars.sh is only available
on your login/frontend nodes,
but not on your compute nodes.
you might be luckier with
/opt/intel/mkl/bin/mklvars.sh

an other option is to
ldd /home/emoujaes/Elie/SPRKKR/bin/kkrscf6.3MPI
on your login node, and explicitly set the LD_LIBRARY_PATH in your PBS script

if /opt/intel/composer_xe_2013_sp1/mkl/lib/intel64 is available on your compute
nodes, you might want to append
-Wl,-rpath,/opt/intel/composer_xe_2013_sp1/mkl/lib/intel64
to LIB
/* if you do that, keep in mind you might not automatically use the most up to
date mkl lib when they get upgraded by your sysadmin */

-Wl,-rpath,/path/to/intel/compiler/install/lib/intel64,-rpath,/path/to/intel/compiler/install/mkl/lib/intel64



Regards,
Thomas Jahns

We found the most reliable solution was to have in the place ifort/icc/icpc reside to have a file for each compiler named ifort.cfg, icc.cfg and icpc.cfg respectively that contains a single line like this: that lets individual users still override the run-time library version used with LD_LIBRARY_PATH, but setting it is no longer needed for regular users who get binaries that also work when they haven't setup the environment for some specific intel compiler. An alternative is static linking but that has other downsides.

smime.p7s
Description: S/MIME Cryptographic Signature