Hi Nicolas! Nicolas Morey-Chaisemartin writes:

Le 10/22/20 à 10:57 AM, Egbert Eich a écrit :

...

Hi Nicolas,

Nicolas Morey-Chaisemartin writes:

...

...

Is this available or all MPI flavors? If so, we could just do a: BuildRequires: %{mpi}-macros-devel

No it's only for openmpi* packages at the moment.

Ok, if you can fix this for mpich and mvapich we can integrate this into more packages. I'd be easier if we were able to do things the same way for all MPI flavors.

...

The define of %mpi should be avaiable to the build dependency script as it doesn't depend on other macro packages. If this is the case I will make adjustments when visiting packages again.

...

It'll provide the macros: %setup_openmpi # (Load the orpper mpivars.sh) %openmpi_requires # ( Add the right Requires:..... for the openmpi package) %openmpi_devel_requires # same but for devel packages)

Also for using the "default" version of openmpi (currently openmpi2), you can juste BuildRequires: openmpi-macros-devel. It'll pull the macros from the default version so there is no need to specify which one and it can be changed more easily when we decide to go to openmpi 3 or 4 by default.

Right. Ok, this should work as well - if 'openmpi' stands for 'openmpi-default' instead of 'openmpi1' it'd be fine.

Right.

It does. That's the reason openmpi was renamed to openmpi1

We will

...

build for openmpi2 twice then: once for 'default' and once for it explicitly and we don't build for openmpi1 at all. But maybe people don't care any more ...

You probably don't need that. The default flavor is mostly for package which don't really care which one they use (stuff like boost and other core libs) but you need all of them to use the same one. It was introduced as there was a huge mess of some libs building against openmpi1, some against openmpi2 so the stack wasn't working. Package like lapack where the pick of flavor might matter should build against all, not necesseraly against the default one.

Yes. I would think for many of the packages in science this is true. With multibuild this will be quite easy - one does not necessarily need all the HPC stuff with full environment module support. Thanks! Cheers, Egbert.-- To unsubscribe, e-mail: opensuse-science+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-science+owner@opensuse.org