Re: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries.
On Linux and Mac, Intel c and c++ are sufficiently compatible with gcc and g++ that this should be possible. This is not so for Fortran libraries or Windows. Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone Original message From: Michael Thomadakis Date: 9/18/17 3:51 PM (GMT-05:00) To: users@lists.open-mpi.org Subject: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries. Dear OpenMPI list, As far as I know, when we build OpenMPI itself with GNU or Intel compilers we expect that the subsequent MPI application binary will use the same compiler set and run-times. Would it be possible to build OpenMPI with the GNU tool chain but then subsequently instruct the OpenMPI compiler wrappers to use the Intel compiler set? Would there be any issues with compiling C++ / Fortran or corresponding OMP codes ? In general, what is clean way to build OpenMPI with a GNU compiler set but then instruct the wrappers to use Intel compiler set? Thanks!Michael ___ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
Re: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries.
I think Jeff squires summed it up. Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone Original message From: Michael Thomadakis Date: 9/18/17 4:57 PM (GMT-05:00) To: Open MPI Users Cc: n8tm Subject: Re: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries. Thanks for the note. How about OMP runtimes though? Michael On Mon, Sep 18, 2017 at 3:21 PM, n8tm via users wrote: On Linux and Mac, Intel c and c++ are sufficiently compatible with gcc and g++ that this should be possible. This is not so for Fortran libraries or Windows. Sent via the Samsung Galaxy S8 active, an AT&T 4G LTE smartphone Original message From: Michael Thomadakis Date: 9/18/17 3:51 PM (GMT-05:00) To: users@lists.open-mpi.org Subject: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries. Dear OpenMPI list, As far as I know, when we build OpenMPI itself with GNU or Intel compilers we expect that the subsequent MPI application binary will use the same compiler set and run-times. Would it be possible to build OpenMPI with the GNU tool chain but then subsequently instruct the OpenMPI compiler wrappers to use the Intel compiler set? Would there be any issues with compiling C++ / Fortran or corresponding OMP codes ? In general, what is clean way to build OpenMPI with a GNU compiler set but then instruct the wrappers to use Intel compiler set? Thanks!Michael ___ 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] Typo in mpi-fort-wrapper-data.txt?
Most Linux distros ignore repetition of forward slash. Sometimes used as excuse
for sloppiness.
Sent via the Samsung Galaxy S8 Active, an AT&T 4G LTE smartphone
Original message From: Joshua Wall
Date: 1/30/18 10:28 AM (GMT-05:00) To: users@lists.open-mpi.org Subject:
[OMPI users] Typo in mpi-fort-wrapper-data.txt?
Hello users,
I was installing a new OS this week (Xubuntu 17.10 to be exact) and pulled
down the latest OMPI from apt on the machine. While trying to compile a MPI
Fortran program I noticed the following:
josh@josh-UX490UA:/usr/share/openmpi$ mpifort --showme
gfortran -I/usr/lib/x86_64-linux-gnu/openmpi/include -pthread
-I/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr//lib
-L/usr/lib/x86_64-linux-gnu/openmpi/lib -lmpi_usempif08 -lmpi_usempi_ignore_tkr
-lmpi_mpifh -lmpi
Noticing the double //, I checked the file and saw it there also:
josh@josh-UX490UA:/usr/share/openmpi$ sudo vim mpifort-wrapper-data.txt
# There can be multiple blocks of configuration data, chosen by
# compiler flags (using the compiler_args key to chose which block
# should be activated. This can be useful for multilib builds. See the
# multilib page at:
# https://github.com/open-mpi/ompi/wiki/compilerwrapper3264
# for more information.
project=Open MPI
project_short=OMPI
version=2.1.1
language=Fortran
compiler_env=FC
compiler_flags_env=FCFLAGS
compiler=gfortran
preprocessor_flags=
compiler_flags=-pthread -I${libdir}
linker_flags=-L/usr//lib
# Note that per https://svn.open-mpi.org/trac/ompi/ticket/3422, we
# intentionally only link in the MPI libraries (ORTE, OPAL, etc. are
# pulled in implicitly) because we intend MPI applications to only use
# the MPI API.
libs=-lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi
libs_static=-lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi
-lopen-rte -lopen-pal -lhwloc -ldl -lutil -lm
dyn_lib_file=libmpi.so
static_lib_file=libmpi.a
required_file=
includedir=${includedir}
libdir=${libdir}
I'm guessing this is unintentional, but wanted to check since its in the distro
before I edit it on my end.
Thanks,
Josh
--
Joshua Wall
Doctoral Candidate
Department of Physics
Drexel University
3141 Chestnut Street
Philadelphia, PA 19104
___
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
