<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=""><div class=""><br class=""></div> It seems like this might be a good strategy, presumably the directory is already made to hold mpi.h for MPI uni<div class=""><br class=""></div><div class=""> <span style="font-size: 13px;" class="">Perhaps its possible to change our installer to have mpiuni's mod file at prefix/include/petsc/mpiuni/mpi.mod - [to enable reusing mpi.mod name ]</span><br style="font-size: 13px;" class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 18, 2021, at 4:36 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="">Sure - that's the trade-off.<br class=""><br class="">At some point I think we decided not to map mpiuni.mod to mpi.mod [to avoid potential clash with other mpi/mpiuni type impls].<br class=""><br class="">If I remember correctly - we could limit on the C side - by not installing mpi.h in std location [its at include/petsc/mpiuni/mpi.h]<br class=""><br class="">And since mpiuni's mpi.mod is to be installed in prefix/include - I think this different name was chosen.<br class=""><br class="">And now that we are supporting 'use mpi or mpi_f08' - its 'use mpiuni or mpi or mpi_f08' or use --with-mpi-f90module-visibility=1<br class=""><br class="">For now petscmpi maps to mpi or mpiuni.<br class=""><br class="">Perhaps its possible to change our installer to have mpiuni's mod file at prefix/include/petsc/mpiuni/mpi.mod - [to enable reusing mpi.mod name ]<br class=""><br class="">[at some point we had an option to skip fortran mpi_comm_rank() etc - as they would clash with similar uni impls. But I see that option no longer exists?]<br class=""><br class="">Satish<br class=""><br class="">On Sat, 18 Dec 2021, Barry Smith wrote:<br class=""><br class=""><blockquote type="cite" class=""><br class=""> Urg, this is pretty horrible. petscmpi? Why can't MPIUNI provide this as "standard" MPI modules?<br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class="">On Dec 18, 2021, at 11:04 AM, Satish Balay via petsc-users <<a href="mailto:petsc-users@mcs.anl.gov" class="">petsc-users@mcs.anl.gov</a>> wrote:<br class=""><br class="">Ah - you need 'use petscmpi'<br class=""><br class="">For example: ksp/ksp/tutorials/ex44f.F90<br class=""><br class="">Satish<br class=""><br class="">On Sat, 18 Dec 2021, Matthew Knepley wrote:<br class=""><br class=""><blockquote type="cite" class="">On Sat, Dec 18, 2021 at 9:26 AM Tabrez Ali <<a href="mailto:tabrezali@gmail.com" class="">tabrezali@gmail.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">I am trying to compile Fortran code with PETSc 3.16 built without MPI,<br class="">i.e., --with-mpi=0, and am getting the following error:<br class=""><br class=""> call MPI_Comm_rank(MPI_COMM_WORLD,rank,ierr)<br class=""> 1<br class="">Error: Symbol ‘mpi_comm_world’ at (1) has no IMPLICIT type<br class=""><br class=""></blockquote><br class="">Hi Tabrez,<br class=""><br class="">The definition of MPI_COMM_WORLD is in mpif.h. Are you #including that?<br class=""><br class=""> Thanks,<br class=""><br class=""> Matt<br class=""><br class=""><br class=""><blockquote type="cite" class="">There are no issues with PETSc 3.14 or prior versions. Any ideas as to<br class="">what could be wrong?<br class=""><br class="">I do see the following note (below) in<br class=""><a href="https://petsc.org/main/docs/changes/315/" class="">https://petsc.org/main/docs/changes/315/</a> but I am not sure if it's<br class="">related:<br class=""><br class="">*Add configure option --with-mpi-f90module-visibility [default=``1``].<br class="">With 0, mpi.mod will not be visible in use code (via petscsys.mod) -<br class="">so mpi_f08 can now be used*<br class=""><br class="">Regards,<br class=""><br class="">Tabrez<br class=""><br class=""></blockquote><br class=""><br class=""><br class=""></blockquote></blockquote></blockquote></div></div></blockquote></div><br class=""></div></body></html>