On Wed, Dec 22, 2021 at 5:45 PM Tom Kacvinsky <tkacv...@gmail.com> wrote: > > On Wed, Dec 22, 2021 at 4:11 PM Matt Thompson <fort...@gmail.com> wrote: > > > > All, > > > > When I build Open MPI with NAG, I have to pass in: > > > > FCFLAGS"=-mismatch_all -fpp" > > > > this flag tells nagfor to downgrade some errors with interfaces to warnings: > > > > -mismatch_all > > Further downgrade consistency checking of procedure > > argument lists so that calls to routines in the same file which are > > incorrect will produce warnings instead of error messages. > > This option disables -C=calls. > > > > The fpp flag is how you tell NAG to do preprocessing (it doesn't > > automatically do it with .F90 files). > > > > I also have to pass in a lot of other flags as seen here: > > > > https://github.com/mathomp4/parcelmodulefiles/blob/main/Compiler/nag-7.1_7101/openmpi/4.1.2.lua > > > > Now I hadn't yet tried NAG 7.1 with Open MPI because NAG 7.1 has a bug with > > a library I depend on, but it does promise better F2008 support. To see > > what happens, I tried myself and added --enable-mpi-fortran=all, but: > > > > checking if building Fortran 'use mpi_f08' bindings... no > > configure: error: Cannot build requested Fortran bindings, aborting > > > > Unfortunately, the NAG Fortran guru I work with is off until the new year. > > When he comes back, I might ask him about this. He might know something we > > can do to make NAG happy with mpif08. > > > > The very curious thing about this is that NAG 7.1 is that mpif08 > configured properly with the macOS (Intel architecture) flavor of > it. But as this thread seems to indicate, it barfs on Linux. Just > an extra data point. >
I'd like to recall that statement, I was not looking at the config.log carefully enough. I see this still, even on macOS checking if building Fortran 'use mpi_f08' bindings... no
