Mailinglist Archive: opensuse-factory (188 mails)

< Previous Next >
Re: [opensuse-factory] openMPI mixup in Tumbleweed/Leap 15.x
  • From: Chris Coutinho <chrisbcoutinho@xxxxxxxxx>
  • Date: Sun, 9 Dec 2018 11:02:19 +0100
  • Message-id: <20181209100219.i3mnm3pkeigm4mrw@tumbleweed>
For what it's worth, I use `mpi-selector` to set a system-wide MPI implementation and then switch between them. This keeps MPI libraries from clashing when I build software from source.

I'm not sure if the openSUSE packages use this method, but it works for packages I build myself really well. Are you building hdf5 and/or netcdf yourself?


On Dec-08-18, Stefan Brüns wrote:

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:

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

As both libraries ( and 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:

Kind regards,


[1] "Stay with openmpi(1) also on PPC", boost, 2018-10-01, https://
[2] "Cntk packages do not support OpenMPI 2+",

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

< Previous Next >
Follow Ups