We set things up like this, things built with system compiler and libs outside of EasyBuild (/lap == Locally Added Packages, this is where we used to install everything we built before EB) /lap/pmix, /lap/ucx, /lap/libevent, /lap/slurm (And several versions of each below those dirs)
Slurm is built against those installations of pmix and ucx, and pmix is built against that libevent. The EasyBuild software tree is completely separate and the PMIx builds there are only used when building OpenMPI. And for pointing IntelMPI to an EasyBuild controlled PMIx version of libpmi.so Slurm is classified as system software and complete separate from the EB tree, and thus needs to have support libraries (pmix/ucx etc) complete separated too. The turnaround for new versions of PMIx/UCX used for building Slurm are much slower since we only do that when there is a new version of Slurm since there is no reason to change that until Slurm actually supports a newer version... On 2/18/20 4:20 PM, Loris Bennett wrote: > Åke Sandgren <[email protected]> writes: > >> Since Slurm is built with the system compiler you should also build its >> PMIx/UCX builds with the system compiler (and the corresponding libevent >> in case you don't use the system version), and keep them separate from >> the EB installation. > > Sorry, I'm confused again. Do you mean that the PMIx versions should be > built with the system compiler and *without* using EB? > > But aren't I still going to need to install PMIx via EB to allow adding > PMIx as a dependency for OpenMPI via a hook? -- Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden Internet: [email protected] Phone: +46 90 7866134 Fax: +46 90-580 14 Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se
