<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi Cristof, <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thanks for the bug report. Looks like our configure script is checking for the file
<code>slurm/pmi2.h</code> while the actual file includes <code>pmi.h</code> without the slurm prefix. This include was changed in 3.0 to support non-slurm installations of pmi2. The easiest way to solve this is to set the environment variable
<code>CPATH=/usr/include/slurm:$CPATH</code> (or using whatever path your slurm include directory resides on). Alternatively, you can add
<code>MPICHLIB_CFLAGS=-I/usr/include/slurm</code> as an argument to configure.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Either of the above options should get you past the build error for now. We will also look into having our configure script automatically detect slurm based pmi installations and adapt the paths appropriately. As a final note, we do recomend using pmi1 with
slurm when possible (as do the upstream developers of MPICH) as it is a more stable and standardized provider than pmi2, which was never completed. Slurm's
<code>--with-mpi=pmi2</code> actually supports both the pmi1 and and pmi2 interface.
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Please let me know if you have any further issues building MVAPICH 3.0a.<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thanks,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Nat<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Mvapich-discuss <mvapich-discuss-bounces+shineman.5=osu.edu@lists.osu.edu> on behalf of christof.koehler--- via Mvapich-discuss <mvapich-discuss@lists.osu.edu><br>
<b>Sent:</b> Wednesday, May 10, 2023 04:06<br>
<b>To:</b> mvapich-discuss@lists.osu.edu <mvapich-discuss@lists.osu.edu><br>
<b>Subject:</b> [Mvapich-discuss] mvapich2 3.0a build failure finding pmi2.h</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hello everybody,<br>
<br>
we have an Cornelis Omni-Path system and therefore would like to start<br>
testing mvapich2 3.0a. However, I am currently unable to build it.<br>
I would like to add that building mvpaich2 2.3.7-1 with slurm/pmi2 on<br>
the same system works fine.<br>
<br>
For mvapich2 3.0a the configure step using<br>
FFLAGS=-fallow-argument-mismatch ./configure --with-pm=slurm --with-pmi=pmi2<br>
succeeds.<br>
<br>
But in the make step the build stops with<br>
<br>
make[2]: Entering directory '/backup1/build_temp/mvapich2-3.0a'<br>
CC src/mpi/attr/lib_libmpi_la-attr_delete.lo<br>
In file included from ./src/include/mpiimpl.h:130,<br>
from src/mpi/attr/attr_delete.c:6:<br>
./src/include/mpir_pmi.h:18:10: fatal error: pmi2.h: No such file or<br>
directory<br>
18 | #include <pmi2.h><br>
| ^~~~~~~~<br>
compilation terminated.<br>
<br>
In fact we have /usr/include/slurm/pmi2.h and this is apparently picked<br>
up correctly by configure:<br>
<br>
> grep pmi2.h configure.out <br>
checking slurm/pmi2.h usability... yes<br>
checking slurm/pmi2.h presence... yes<br>
checking for slurm/pmi2.h... yes<br>
<br>
So this is a bit confusing. Also, because according to the mailing list<br>
some people already built it and did not report such an error.<br>
<br>
I attach the gzipped config.log, the configure stdout (configure.out) and <br>
the stdout of the make step (make.out) to this email.<br>
<br>
Best Regards<br>
<br>
Christof<br>
<br>
-- <br>
Dr. rer. nat. Christof Köhler email: c.koehler@uni-bremen.de<br>
Universitaet Bremen/FB1/BCCMS phone: +49-(0)421-218-62334<br>
Am Fallturm 1/ TAB/ Raum 3.06 fax: +49-(0)421-218-62770<br>
28359 Bremen <br>
</div>
</span></font></div>
</body>
</html>