To be clear, --prefix and OPAL_PREFIX do two different things:
1. "mpirun --prefix" and "/abs/path/to/mpirun" (both documented in mpirun(1))
are used to set PATH and LD_LIBRARY_PATH on remote nodes when invoked via
ssh/rsh. It's a way of not having to set your shell startup files to point to
a
> Am 10.04.2019 um 14:57 schrieb Dave Love :
>
> In fact, setting OPAL_PREFIX doesn't work for a relocated tree (with
> OMPI 1.10 or 3.0). You also need $OPAL_PREFIX/lib and
> $OPAL_PREFIX/lib/openmpi on LD_LIBRARY_PATH (assuming $MPI_LIB=$MPI_HOME/lib):
>
> $ OPAL_PREFIX=$(pwd)/usr/lib64/open
In fact, setting OPAL_PREFIX doesn't work for a relocated tree (with
OMPI 1.10 or 3.0). You also need $OPAL_PREFIX/lib and
$OPAL_PREFIX/lib/openmpi on LD_LIBRARY_PATH (assuming $MPI_LIB=$MPI_HOME/lib):
$ OPAL_PREFIX=$(pwd)/usr/lib64/openmpi3 ./usr/lib64/openmpi3/bin/mpirun
mpirun true
./usr/
"Jeff Squyres (jsquyres) via users" writes:
> Reuti's right.
>
> Sorry about the potentially misleading use of "--prefix" -- we
> basically inherited that CLI option from a different MPI
> implementation (i.e., people asked for it). So we were locked into
> that meaning for the "--prefix" CLI op
Reuti writes:
>> It should be documented.
>
> There is this FAQ entry:
>
> https://www.open-mpi.org/faq/?category=building#installdirs
For what it's worth, I looked under "running" in the FAQ, as I was after
a runtime switch. I expect FAQs to point to the actual documentation,
though, and an en
Reuti's right.
Sorry about the potentially misleading use of "--prefix" -- we basically
inherited that CLI option from a different MPI implementation (i.e., people
asked for it). So we were locked into that meaning for the "--prefix" CLI
options.
> On Apr 9, 2019, at 9:14 AM, Reuti wrote:
> Am 09.04.2019 um 14:52 schrieb Dave Love :
>
> Reuti writes:
>
>> export OPAL_PREFIX=
>>
>> to point it to the new location of installation before you start `mpiexec`.
>
> Thanks; that's now familiar, and I don't know how I missed it with
> strings.
>
> It should be documented.
There is
Dave,
Can you please post the configure command line of the Open MPI you are trying
to relocate ?
Cheers,
Gilles
Dave Love wrote:
>Reuti writes:
>
>> export OPAL_PREFIX=
>>
>> to point it to the new location of installation before you start `mpiexec`.
>
>Thanks; that's now familiar, and I d
Reuti writes:
> export OPAL_PREFIX=
>
> to point it to the new location of installation before you start `mpiexec`.
Thanks; that's now familiar, and I don't know how I missed it with
strings.
It should be documented. I'd have expected --prefix to have the same
effect, and for there to be an MC
Hi,
> Am 09.04.2019 um 13:31 schrieb Dave Love :
>
> Is it possible to use the environment or mpirun flags to run an OMPI
> that's been relocated from where it was configured/installed? (Say
> you've unpacked a system package that expects to be under /usr and want
> to run it from home without c
Upon reflecting on this more, I guess I see two issues. First, there's
the issue of allowing the user to install our software on the system
where ever they like. Some users may want to install it in their home
directories, others may have a sys admin install it in a common
location. This seems like
Greetings Allen.
This problem has not yet been resolved, but I'm quite sure we have an
open ticket about this on our bug tracker. I just replied to Patrick
on-list about a related issue (his use of --prefix); I'd have to
think about this a bit more, but a solution proposed by one of the
12 matches
Mail list logo
