[Bug 217750] net/openmpi, net/openmpi2 require -rpath when non-default gcc is used
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Mar 13 12:42:05 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217750
Bug ID: 217750
Summary: net/openmpi, net/openmpi2 require -rpath when
non-default gcc is used
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: danilo at FreeBSD.org
Reporter: mexas at bris.ac.uk
Flags: maintainer-feedback?(danilo at FreeBSD.org)
Assignee: danilo at FreeBSD.org
With non-default GCC in /etc/make.conf,
e.g. DEFAULT_VERSIONS=gcc=6 there is an anomaly
between net/mpich, net/openmpi and net/openmpi2.
$ /usr/local/bin/mpif90 --version
GNU Fortran (FreeBSD Ports Collection) 6.3.1 20161229
$ /usr/local/bin/mpif90 z.f90
$ /usr/local/bin/mpirun -np 3 ./a.out
node 1 : Hello world
node 2 : Hello world
node 0 : Hello world
However, with openmpi (same with net/openmpi2):
$ /usr/local/mpi/openmpi/bin/mpif90 --version
GNU Fortran (FreeBSD Ports Collection) 6.3.1 20161229
$ /usr/local/mpi/openmpi/bin/mpif90 z.f90
$ /usr/local/mpi/openmpi/bin/mpirun -np 3 ./a.out
-------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.
-------------------------------------------------------
/lib/libgcc_s.so.1: version GCC_4.6.0 required by
/usr/local/lib/gcc49/libgfortran.so.3 not found
/lib/libgcc_s.so.1: version GCC_4.6.0 required by
/usr/local/lib/gcc49/libgfortran.so.3 not found
so I need to pass -rpath to mpif90:
$ /usr/local/mpi/openmpi/bin/mpif90 -Wl,-rpath="/usr/local/lib/gcc6" z.f90
$ /usr/local/mpi/openmpi/bin/mpirun -np 3 ./a.out
node 0 : Hello world
node 1 : Hello world
node 2 : Hello world
I'd prefer openmpi and openmpi2 to behave as mpich.
This helps ports such as lang/opencoarrays, which can be
built with a selection of MPI ports.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list