Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI users] Fixing Intel Compiler and OpenMPI 1.6.X (or any version)
From: Alan Wild (alan_at_[hidden])
Date: 2013-06-30 15:52:45


I'm surprised that there are users still reporting issues getting this to
work, but as I'm still seeing notes in the digest I wanted to share (what I
believe the issue is) and how I've fixed it.

If you don't take special measures, OpenMPI will be dynamically linked and
have runtime dependencies on several of Intel's .so files. However,
passing LD_LIBRARY_PATH has an option on mpirun is often not sufficient
because the orted process itself has these dyanmic dependencies... so when
you invoke mpirun, it fires up and launches orted on the remote hosts (with
the intention of passing LD_LIBRARY_PATH or whatever to the remote process
but the remote process immediately fails because it cannot resolve its
dependencies (and LD_LIBRARY_PATH is never setup on the far side).

So I see two options:

1) linking orted statically. (Not sure if I've ever done this)

2) Passing an rpath in your openmpi link options so that oreted can resolve
its own dependencies without needing an LD_LIBRARY_PATH

You can do #2 by using something similar to the following on your configure
line

./configure --prefix=/path/to/where/to/install/openmpi
LDFLAGS="-Wl,--enable-new-dtags
-Wl,-rpath,/path/to/intel/compiler/lib_directory"

-Alan

-- 
alan_at_[hidden] http://humbleville.blogspot.com