Hui Zhou

Keep this issue open until * either README is updated and configure issues warning for the user * or configure add nag include path when nagfor is used.

@ThemosTsikas Thanks for chiming in. Is `$(nagfor -# foo.c 2>&1 |grep -o -e '\-I[^ ]*')` the best way to grab standard include path? We can add it to our configure...

User provided `FCFLAGS` is supposed to be included in the wrapper scripts (`mpifort`). I am not sure why `-mismatch` got dropped. I would say the CMake logic is broken as...

> Although I tried providing MPICHLIB_FCFLAGS and MPICHLIB_FFLAGS (to "-f2018 -mismatch"), configure fails telling me I also need FFLAGS set. Is that a feature or a bug? It is a...

> > Although I tried providing MPICHLIB_FCFLAGS and MPICHLIB_FFLAGS (to "-f2018 -mismatch"), configure fails telling me I also need FFLAGS set. Is that a feature or a bug? > >...

> I am not sure you want to include "-mismatch" in the installed mpif90 & scripts. Standard-compliant Fortran programs will lose some of the checking abilities of the NAG Compiler...

> The NAG Compiler ignores IGNORE_TKR pragma. That is unfortunate. That means we have to put `-mismatch` in `mpif90` wrapper or most users won't be able to compile their Fortran...

> A better solution might be to include the option -wmismatch=MPI_xxx,MPI_yyy,MPI_zzz which suppresses consistency checking for the specified procedures. So NAG is able to do per-routine ignore-mismatch! All we need...

> The "-indirect " option will read options from the named file, so you can collect all of the MPI_xxx routines in a file and use that, keeping the command...

Okay, we'll give it a try.