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.
mpirun only does this when it is using the "prefix" functionality,
which is activated in one of a few ways:
- you use the absolute pathname to mpirun
- you use the "--prefix" option to mpirun
- you configured OMPI with the --enable-mpirun-prefix-by-default option
The intent for this functionality is for users who do not want to set
their PATH / LD_LIBRARY_PATH on remote nodes. This is usually most
useful when OMPI is installed in locations that are not already
included in the PATH/LD_LIBRARY_PATH (e.g., /opt/openmpi or somesuch).
On May 7, 2008, at 7:01 PM, Ingo Josopait wrote:
> It seems that mpirun adds /usr/lib64 at the beginning of the
> LD_LIBRARY_PATH environment variable (/usr/lib64 usually corresponds
> /usr/lib on non-amd64 systems):
> $ env | grep LIB
> $ mpirun env | grep LIB
> This would normally not be a problem, but I am trying to overload some
> libraries in the /usr/lib64 directory in order to use the debugging
> of gcc.
> Why is /usr/lib64 added to the library path? Is there a reason for it?
> Or is it some configuration error on my system?
> users mailing list