On Jul 9, 2009, at 10:22 AM, rahmani wrote:
yes, they are intel library and all are in LD_LIBRARY_PATH
/usr/local/openmpi/intel/1.3.2/bin/mpif90 --showme
gfortran -I/usr/local/include -pthread -I/usr/local/lib -L/usr/local/
lib -lmpi_f90 -lmpi_f77 -lmpi -lopen-rte -lopen-pal -ldl -Wl,--
export-dynamic -lnsl -lutil -lm -ldl
ldd /usr/local/openmpi/intel/1.3.2/bin/mpirun
linux-vdso.so.1 => (0x00007fff555fd000)
libopen-rte.so.0 => /usr/local/lib/libopen-rte.so.0
(0x00007fa64d154000)
libopen-pal.so.0 => /usr/local/lib/libopen-pal.so.0
(0x00007fa64cef2000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fa64ccee000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fa64cad6000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007fa64c8d3000)
libm.so.6 => /lib64/libm.so.6 (0x00007fa64c67d000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa64c466000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa64c24a000)
libc.so.6 => /lib64/libc.so.6 (0x00007fa64bef1000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa64d3b2000)
I had another openmpi in my computer. I configure openmpi 1.3 with
gnu compiler and --prefix=/usr/local
I can not use both of them?
You can; you just need to set your LD_LIBRARY_PATH appropriately.
Specifically, when you run "mpirun" (or "mpif90" or ..."), it looks to
find libopen-rte.so. The first one that it is finding is the "wrong"
one -- the one in /usr/local. You therefore get "wrong" results
because it's behaving like the one installed in /usr/local.
You can probably prefix your LD_LIBRARY_PATH with /usr/local/openmpi/
intel/1.3.2/lib and then it'll use the "right" ilibopen-rte.so.
Make sense?
--
Jeff Squyres
Cisco Systems
