[mvapich-discuss] Can I build mvapich2 binaries statically, while compiling the MPI libraries (for the apps) statically

Craig Tierney craig.tierney at noaa.gov
Mon Jul 16 19:25:07 EDT 2012


I am trying to build mvapich2-1.8, and I am running into some difficulties.  I need
to build the MPI libraries from mvapich2 as shared so that other tools (such as HDF5)
can link against them and create shared libraries for them.  The problem is that
when I specify --enable-shared, it makes the mvapich2 utilities like hydra_pmi_proxy
as shared.

We use modules to allow users to specify compilers, none are loaded by default.  When
mpiexec tries to startup an application, it will do something like:

ssh $NODE /$MPICHPATH/bin/hydra_pmi_proxy ......

But it will fail with a library not found because it cannot find the (in this case)
the Intel libraries that were used to compile it.  I can solve this with including:

LDFLAGS="-Wl,-rpath $PATH_TO_COMPILER_LIBRARIES"

While it works it seems less than desirable.

How do others solve this problem?

Thanks,
Craig


More information about the mvapich-discuss mailing list