Hi all -

I'm having a bit of an issue with my library paths and mpi that I can't
quite seem to resolve.

If I run from host-0:
mpirun -np 4 -host host-0 myprogram

I have no problems, but if I run
mpirun -np 4 -host host-1 myprogram

I get an error like this:
error while loading shared libraries: libSGUL.so: cannot open shared object
file: No such file or directory

I can see that it can't find two of my shared library files when I execute
this:
mpirun -np 1 -host host-1 ldd myprogram

       linux-gate.so.1 =>  (0xb7f48000)
       libSGUL.so => not found
       libguile.so.12 => /usr/lib/libguile.so.12 (0xb7e96000)
       libOpenMesh_Core.so => not found
       libmpi_cxx.so.0 => /usr/lib/libmpi_cxx.so.0 (0xb7e7e000)
       libmpi.so.0 => /usr/lib/libmpi.so.0 (0xb7dd9000)
       liborte.so.0 => /usr/lib/liborte.so.0 (0xb7d92000)
       libopal.so.0 => /usr/lib/libopal.so.0 (0xb7d45000)
       libdl.so.2 => /lib/libdl.so.2 (0xb7d41000)
       libnsl.so.1 => /lib/libnsl.so.1 (0xb7d2b000)
       libutil.so.1 => /lib/libutil.so.1 (0xb7d27000)
       libm.so.6 => /lib/libm.so.6 (0xb7d01000)
       libstdc++.so.6 =>
/usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6 (0xb7c22000)
       libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgcc_s.so.1
(0xb7c18000)
       libpthread.so.0 => /lib/libpthread.so.0 (0xb7c01000)
       libc.so.6 => /lib/libc.so.6 (0xb7adb000)
       libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0xb7ad6000)
       libqthreads.so.12 => /usr/lib/libqthreads.so.12 (0xb7ad3000)
       libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7aa5000)
       /lib/ld-linux.so.2 (0xb7f49000)
       linux-gate.so.1 =>  (0xb7f23000)

If I run the following, however, I see that my LD_LIBRARY_PATH is correct:
mpirun -np 1 -host burn-0 echo $LD_LIBRARY_PATH

/usr/local/lib32:/home/budge/local/lib:/home/budge/projects/mgi_tony/build/lib

For now I've had to resort to making mpi run a wrapper script which sets my
LD_LIBRARY_PATH, but naturally this isn't ideal.  Does anyone have an idea
what this is or how I can fix it?

Thanks,
 Brian

Reply via email to