[mvapich-discuss] Using environment modules -- libimf.so not found

Mon Jan 12 17:25:51 EST 2015

Thank you; that did the trick!

Incidentally, I know this is a bit off topic, but one of you may have some idea, and it was originally confusing me related to this problem. I use the Intel compilers, and they appear to ship something called the MPI Runtime, which supplies its own mpiexec/mpirun commands. Does anyone know what this is? It doesn’t appear to be the full-blown Intel MPI implementation, but interestingly enough, it appeared to work to launch jobs in conjunction with MVAPICH2.

Incidentally,. 
> On Jan 12, 2015, at 4:17 PM, Jonathan Perkins <perkinjo at cse.ohio-state.edu> wrote:
> 
> Thanks, I was indeed missing the hyphen in front of the rpath.
> 
> On Mon, Jan 12, 2015 at 04:14:11PM -0500, John DelSignore wrote:
>> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
>> <html>
>> <head>
>>  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
>> </head>
>> <body bgcolor="#ffffff" text="#000000">
>> <br>
>> <br>
>> Jonathan Perkins wrote:
>> <blockquote cite="mid:20150112205819.GB507 at x54c.attlocal.net"
>> type="cite">
>>  <pre wrap="">On Mon, Jan 12, 2015 at 03:01:36PM -0500, Novosielski, Ryan wrote:
>>  </pre>
>>  <blockquote type="cite">
>>    <pre wrap="">Hi all,
>> 
>> Since we use different compilers for different software packages and
>> have a pretty complicated setup for some of the dependencies,
>> generally what we do for submitting jobs is to load the modules on the
>> master node and submit jobs so that the environment variables are
>> passed through. However, this does not appear to be working right for
>> MVAPICH2. LD_LIBRARY_PATH is defined, according to the output of env
>> at the beginning of the submission script, but apparently does not get
>> through to whatever happens when mpiexec/mpirun start the MPI job. The
>> FAQ for MPICH2 recommends making sure the environment is correct for
>> interactive and non-interactive sessions. However, I do not want to
>> define a single PATH to the Intel compiler libraries. People on our
>> systems make use of software compiled with different versions, etc.
>> 
>> Does anyone have an idea of how I might get around this? 
>>    </pre>
>>  </blockquote>
>>  <pre wrap=""><!---->
>> Hi Ryan.  I think that you're close to getting it working but we might
>> need a bit more details on how and when the failure is happening
>> exactly.
>> 
>> With mpirun_rsh I believe your setup will work, however with
>> mpiexec.hydra (mpiexec and mpirun point to this by default) I don't
>> think LD_LIBRARY_PATH will be seen early enough before the proxy
>> attempts to execute on the remote nodes.
>> 
>> If you're willing to rebuild MVAPICH2 you can use RPATH during the build
>> so that the proxy will be able to find its dependencies.
>> 
>> Example:
>>    ./configure ... LDFLAGS='-Wl,rpath,/path/to/intel/lib/dir' ...
>> 
>>  </pre>
>> </blockquote>
>> The "ld" option to set RPATH on Linux is "-rpath" (note the "-"), so I
>> think you want "LDFLAGS='-Wl,-rpath,/path/to/intel/lib/dir'".<br>
>> <br>
>> Cheers, John D.<br>
>> <br>
>> </body>
>> </html>
> 
> -- 
> Jonathan Perkins

____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS      |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | novosirj at rutgers.edu - 973/972.0922 (2x0922)
||  \\  Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
     `'