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
"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
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/
> 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
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
Thanks. The code is here:
https://github.com/mboysan/ping-pong-mpi-tcp
OpenMPI is built using:
./configure --prefix=/PATH_TO_HOME_DIRECTORY/openmpi-4.0.1-install \
--enable-mpi-java
The code builds on a number of other machines. Are there any minimum
java build requirements for Op
