Re: [OMPI users] Error when Building an MPI Java program
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 OpenMPI with Java? At present using a machine with Ubuntu 16.04, GCC 5.4.0 and OpenJDK 9 On 4/9/19 4:10 PM, Jeff Squyres (jsquyres) via users wrote: Can you provide a small, standalone example + recipe to show the problem? On Apr 8, 2019, at 6:45 AM, Benson Muite wrote: Hi Am trying to build an MPI Java program using OpenMPI 4.0.1: I get the following error: Compilation failure /MY_DIRECTORY/ping-pong-mpi-tcp/src/main/java/SocketMainMultiJVM.java:[2,10] error: cannot access MPIException Any suggestions on what I am doing incorrectly? Thanks, Benson ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] relocating an installation
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 specific Open MPI installation on remote nodes. This is helpful for users who tend to swap between multiple Open MPI installations. 2. OPAL_PREFIX overrides the compiled-in location in Open MPI binaries and libraries for where it should find things like plugins and help files. It is intended for use when you relocate Open MPI installations. These two can be used in conjunction with each other, if desired, but they are intended for two different purposes. > On Apr 10, 2019, at 9:06 AM, Reuti wrote: > > >> 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/openmpi3 ./usr/lib64/openmpi3/bin/mpirun >> mpirun true >> ./usr/lib64/openmpi3/bin/mpirun: error while loading shared libraries: >> libopen-rte.so.40: cannot open shared object file: No such file or directory > > Does export this OPAL_PREFIX also to all child processes? For me using export > OPAL_PREFIX=… beforehand worked up to now. > > -- Reuti > ___ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users -- Jeff Squyres jsquy...@cisco.com ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] relocating an installation
> 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/openmpi3 ./usr/lib64/openmpi3/bin/mpirun > mpirun true > ./usr/lib64/openmpi3/bin/mpirun: error while loading shared libraries: > libopen-rte.so.40: cannot open shared object file: No such file or directory Does export this OPAL_PREFIX also to all child processes? For me using export OPAL_PREFIX=… beforehand worked up to now. -- Reuti ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] relocating an installation
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/lib64/openmpi3/bin/mpirun: error while loading shared libraries: libopen-rte.so.40: cannot open shared object file: No such file or directory ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] relocating an installation
"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 options. Reading more closely, I see it's only for remote hosts anyhow, but I'd be surprised if only binaries and libraries were relocated from one tree, and only hosts that somehow were distinguished from the one invoking mpirun (et al). Regardless, is there some problem just documenting the relevant variables in the obvious places? ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] relocating an installation
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 environment variables section of the man pages seems the right place. [I know you're only providing info, thanks.] ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
