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.

From: Michael Kluskens (mklus_at_[hidden])
Date: 2006-10-12 10:27:43

On Oct 11, 2006, at 10:38 AM, Lisandro Dalcin wrote:

> On 10/11/06, Jeff Squyres <jsquyres_at_[hidden]> wrote:
>> Open MPI v1.1.1 requires that you set your LD_LIBRARY_PATH to
>> include the
>> directory where its libraries were installed (typically, $prefix/
>> lib). Or,
>> you can use mpirun's --prefix functionality to avoid this
> BTW, Why mpicc/mpicxx does not symply pass a -rpath/-R flag to the
> linker? Do you want to select libraries at runtime? There are
> portability problem in some target plataform? This behavior can be
> really useful to experienced unix users/developers but I am not sure
> if this holds true for all users.

It appears that you want to hardcode the path to libraries in the

That is a very bad thing to do.

Example: you compile your code on your system and run the code on
someone else's system.

Not everyone distributes source code and not everyone wants to
compile source code.