[slurm-users] SLES 15 rpmbuild from 20.02.5 tarball wants munge-libs: system munge RPMs don't provide it
Kevin Buckley
Kevin.Buckley at pawsey.org.au
Mon Oct 26 03:07:31 UTC 2020
On 2020/10/22 16:32, Christian Goll wrote:
>
> The problem comes from the fact that libmunge is part of the SLE-HPC
> module and not part of SLE itself. As soon as you activate this module
> with SUSEConnect you should be able to build it.
>
> The best way to create rpms for SUSE systems is not to use rpmbuild
> directly, but to use the open build service available via
> build.opensuse.org with which you can also build packages for other (not
> only rpm) based distributions. As only downside you have to create and
> account there. In order to build the packages locally, you will have to
> install the package 'osc' and have sudo rights on the system. Now you
> can checkout the slurm sources from openSUSE and build them with
> osc co network:cluster slurm
> cd network:cluster/slurm
> vim slurm.spec
> osc build --ccache -k . SLE_15_SP1
> which will a local build of the slurm packages and will drop these rpms
> in build directory.
>
> kind regards,
> Christian
>
Thanks for that SUSE background info Christian: wasn't aware of that.
Typically, we only rebuild Slurm for the SLES underneath the Cray CLE,
which, as was noted earlier in the thread, means one is building against
a Cray-built munge anyway, and where one does do an "rpmbuild -ta", albeit
from inside a Cray provided wrapper script that sets a few options along
the way.
I was knocking up a VirtualBox SLES15/Slurm testbed on a laptop, so the
connectivity to build.opensuse.org wasn't something I would have thought
of.
Cheers again,
Kevin
--
Supercomputing Systems Administrator
Pawsey Supercomputing Centre
More information about the slurm-users
mailing list