Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

problem with libimf.so.6 again

zws
Beginner
529 Views
I am using IA64/RHLinux AS3.0 with kernel 2.4.21-20.EL. non commercial cc90 and fc90 compiler, mpich-1.2.7.
the installation paths are:
compiler: /apps/intel/cc/9.0
/fc/9.0
mpich: /apps/intel/mpich-1.2.7
I have exported LD_LIBRARY_PATH as /apps/intel/fc/9.0/lib
in /etc/profile.
and also configured it in /etc/ld.so.conf, and the ifortvars.sh
was configured as:
if [ -z "${LD_LIBRARY_PATH}" ]
then
LD_LIBRARY_PATH="/apps/intel/fc/9.0/lib"; export LD_LIBRARY_PATH
else
LD_LIBRARY_PATH="/apps/intel/fc/9.0/lib:$LD_LIBRARY_PATH"; export LD_LIBRARY_PATH
fi
the application compiled and linked correctly but get error at runtime.
the detailedmessagecan beas:
[test@cn115-ib fort]$ mpif90 -c yacobi.f90
[test@cn115-ib fort]$ mpif90 -o yacobi yacobi.o
[test@cn115-ib fort]$ mpirun -np 4 yacobi
/home/users/hpc/test/fort/yacobi: error while loading shared libraries: libimf.so.6: cannot open shared object file: No such file or directory
p0_8737: p4_error: Child process exited while making connection to remote process on cn116-ib: 0
Killed by signal 2.
forrtl: error (69): process interrupted (SIGINT)
lddp0_8737: (4.703125) net_send: could not write to fd=4, errno = 32
[test@cn115-ib fort]$ ldd yacobi
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x2000000000054000)
librt.so.1 => /lib/tls/librt.so.1 (0x2000000000084000)
libimf.so.6 => /apps/intel/fc/9.0/lib/libimf.so.6 (0x20000000000bc000)
libm.so.6.1 => /lib/tls/libm.so.6.1 (0x2000000000350000)
libunwind.so.6 => /apps/intel/fc/9.0/lib/libunwind.so.6 (0x20000000003e0000)
libc.so.6.1 => /lib/tls/libc.so.6.1 (0x2000000000418000)
/lib/ld-linux-ia64.so.2 => /lib/ld-linux-ia64.so.2 (0x2000000000000000)
wath waswrongwith my configuration?
0 Kudos
2 Replies
TimP
Honored Contributor III
529 Views
If you are running MPI across multiple nodes, using shared libraries, LD_LIBRARY_PATH must be set properly, and the libraries present, on each node.
0 Kudos
Intel_C_Intel
Employee
529 Views
To get around this problem, just link the Intel libraries statically using the -i-static option. That way you don't need to worry about them.
0 Kudos
Reply