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

[Jonathan Perkins]

It seems like using the rpath as you've mentioned is a good solution.
An alternative to this us setting LD_LIBRARY_PATH in your mvapich2-icc
module.  Both approaches have their pros and cons but seem to work.

On Mon, Jul 16, 2012 at 05:25:07PM -0600, Craig Tierney wrote:
> 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
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
> 

-- 
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo