Mailinglist Archive: opensuse-factory (188 mails)

< Previous Next >
[opensuse-factory] openMPI mixup in Tumbleweed/Leap 15.x
  • From: Stefan Brüns <stefan.bruens@xxxxxxxxxxxxxx>
  • Date: Sat, 8 Dec 2018 20:53:20 +0100
  • Message-id: <4888842.SdDbd9aPHH@pebbles>
Hi,

I went through a few packages which have an openMPI dependency or support, and
found it quite mixed up:

Currently, we have openmpi(1), openmpi2 and openmpi3 in Leap and TW. While
openmpi3 is currently unused, openmpi1 and openmpi2 are both used, with
similar frequency:

https://build.opensuse.org/package/binary/openSUSE:Factory/openmpi2:standard/
standard/x86_64/openmpi2-libs-2.1.5-2.1.x86_64.rpm
https://build.opensuse.org/package/binary/openSUSE:Factory/openmpi:standard/
standard/x86_64/openmpi-libs-1.10.7-21.1.x86_64.rpm

Several programs will end up with implicitly linking to both versions, as
libnetcdf and hdf5 use openmpi1 and boost_mpi uses openmpi2. One example is
vtk.

As both libraries (libmpi.so.12 and libmpi.so.20) export the same symbols for
large parts, this is mayhem waiting to happen.

For SLE, different MPI versions/implementations are supported using the HPC
modules, but for Leap/TW, we should obviously stick with *one* single
canonical version.

Question now, which version to choose?

Apparently, openmpi2 does not work on all architectures (PPC, PPC64BE) [1],
and is not supported by some software packages [2].

Are there any drawbacks for using openmpi1 everywhere in TW/Leap 15.x?

I have opened a bug report: https://bugzilla.opensuse.org/show_bug.cgi?
id=1118861

Kind regards,

Stefan


[1] "Stay with openmpi(1) also on PPC", boost, 2018-10-01, https://
build.opensuse.org/request/show/639401
[2] "Cntk packages do not support OpenMPI 2+", https://github.com/Microsoft/
CNTK/issues/3197

--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
< Previous Next >