[mpich-discuss] troubles with 3.3.2 and libslurm

Per Berg peb at fcoo.dk
Fri May 29 04:56:16 CDT 2020

Thank you for the quick answer; it is much appreciated.

Your suggestion seems to do the trick. Thanks a lot!


From: Zhou, Hui <zhouh at anl.gov>
Sent: 28 May 2020 22:12
To: discuss at mpich.org
Cc: Per Berg
Subject: Re: [mpich-discuss] troubles with 3.3.2 and libslurm

Unfortunately, there isn’t an easy way not to link with some optional libraries that is available on the building host. Probably at some point we’ll clean up our configure scripts to approach optional libraries more consistently. For now, all I can suggest is to hack it: modify `src/pm/hydra/configure.ac`, search for `have_libslurm`, it should land you somewhere that has `AC_CHECK_HEADERS` and `AC_CHECK_LIB` for slurm, delete both. Re-run `autogen.sh` follow by the usual `configure` and `make`.

Hui Zhou

From: Per Berg via discuss <discuss at mpich.org>
Reply-To: "discuss at mpich.org" <discuss at mpich.org>
Date: Thursday, May 28, 2020 at 3:13 AM
To: "discuss at mpich.org" <discuss at mpich.org>
Cc: Per Berg <peb at fcoo.dk>
Subject: [mpich-discuss] troubles with 3.3.2 and libslurm


I have version 3.2 running smoothly. Now I want to upgrade to vers 3.3.2, but I get a problem that the libslurm.so is required by the mpiexec in v3.3.2. This is a pitty since I don't have that on the compute nodes (and I don't use slurm). In vers3.2 this was not a problem.

I use the same compiler suite and the same configure arguments for both versions (except prefix path, of course).

>From ldd on the mpiexec from v3.3.2 I get:

    libslurm.so.29 => /usr/lib64/libslurm.so.29 (0x00007fc91ebf8000)

which will eventually lead to runtime errors when running across nodes that don't have it.

As said, vers3.2 doesn't have the slurm lib path burned into the mpiexec (and I don't need it).

How do I get rid of the libslurm in mpiexec? Which combination of configure args should I use? I have tried a tons of different args, but without success.

Please, help.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20200529/ae9899d5/attachment.html>

More information about the discuss mailing list