<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">For now, I’ve merely removed the runtime error from there <a href="https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31#379d0ed64a11c2a30793be16c20a756695f74407_515_513" class="">https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31#379d0ed64a11c2a30793be16c20a756695f74407_515_513</a><div class="">And configure seems to be happy (for now… my Windows VM is way to slow…) <a href="http://joliv.et/configure_msmpi.log" class="">http://joliv.et/configure_msmpi.log</a></div><div class="">I will try your diff as well (in about one hour and a half when the first build is through).</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Pierre</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 24 Mar 2021, at 3:10 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov" class="">balay@mcs.anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Wed, 24 Mar 2021, Pierre Jolivet wrote:<br class=""><br class=""><blockquote type="cite" class=""><br class=""><br class=""><blockquote type="cite" class="">On 24 Mar 2021, at 2:55 PM, Matthew Knepley <<a href="mailto:knepley@gmail.com" class="">knepley@gmail.com</a>> wrote:<br class=""><br class="">On Wed, Mar 24, 2021 at 9:37 AM Pierre Jolivet <<a href="mailto:pierre@joliv.et" class="">pierre@joliv.et</a> <<a href="mailto:pierre@joliv.et" class="">mailto:pierre@joliv.et</a>>> wrote:<br class="">Hello,<br class="">It seems mpi.mod is now mandatory <a href="https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31" class="">https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31</a> <<a href="https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31" class="">https://gitlab.com/petsc/petsc/-/commit/68bd534a466d12bdec28b4c298b715271ec2dd31</a>>.<br class="">mpi.mod is not shipped by MS-MPI.<br class="">I want to build MUMPS through PETSc and don’t really care about the Fortran PETSc interface on our Windows boxes (--with-fortran-interfaces=0).<br class=""><br class="">I think you want --with-fc=0, which should turn off this check.<br class=""></blockquote><br class="">No, I have gfortran, I want to compile MUMPS with PETSc, that won’t work --with-fc=0.<br class="">Also, the error message in the configure is wrong, it should read "PETSc Fortran bindings” (not “fortran interface”), and in my email, one should replace --with-fortran-interfaces by --with-fortran-bindings, sorry about that.<br class="">I guess there is a missing check before raise RuntimeError('mpi.mod not found! PETSc fortran interface requires a working mpi.mod'), like if self.argDB['with-fortran-interfaces']<br class="">But I don’t know if that makes sense.<br class=""></blockquote><br class="">I guess you mean:<br class=""><br class="">diff --git a/config/BuildSystem/config/packages/MPI.py b/config/BuildSystem/config/packages/MPI.py<br class="">index 7ea2716cc5..5a1baff9f9 100644<br class="">--- a/config/BuildSystem/config/packages/MPI.py<br class="">+++ b/config/BuildSystem/config/packages/MPI.py<br class="">@@ -497,7 +497,7 @@ Unable to run hostname to check the network')<br class=""><br class=""> def FortranMPICheck(self):<br class=""> '''Make sure fortran include [mpif.h] and library symbols are found'''<br class="">- if not hasattr(self.compilers, 'FC'):<br class="">+ if not hasattr(self.compilers, 'FC') or not self.argDB['with-fortran-bindings']:<br class=""> return 0<br class=""> # Fortran compiler is being used - so make sure mpif.h exists<br class=""> self.libraries.pushLanguage('FC')<br class=""><br class="">If MS-MPI is missing mpi.mod - I guess we'll have to revert this requirement. For some reason the tests in CI don't error out. I'll have to check.<br class=""><br class="">I can add back mpif.h usage [without the extra complex code we had for handling some corner cases - in this mode]<br class=""><br class="">Satish<br class=""><br class=""><blockquote type="cite" class=""><br class="">Thanks,<br class="">Pierre<br class=""><br class=""><blockquote type="cite" class=""> Thanks,<br class=""><br class=""> Matt<br class=""><br class="">Yet, I’m now hit by:<br class="">*******************************************************************************<br class=""> UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):<br class="">-------------------------------------------------------------------------------<br class="">mpi.mod not found! PETSc fortran interface requires a working mpi.mod<br class="">*******************************************************************************<br class="">Could this be fixed somehow, please?<br class="">Thanks,<br class="">Pierre<br class=""><br class=""><br class="">-- <br class="">What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br class="">-- Norbert Wiener<br class=""><br class=""><a href="https://www.cse.buffalo.edu/~knepley/" class="">https://www.cse.buffalo.edu/~knepley/</a> <<a href="http://www.cse.buffalo.edu/~knepley/" class="">http://www.cse.buffalo.edu/~knepley/</a>><br class=""></blockquote></blockquote></div></div></blockquote></div><br class=""></div></body></html>