Question: Are there any compiler vendor supplied modules other than `ifport ifnls ifcore ifposix` that one would anticipate a user calling if they are writing native (not cross-compiled) Fortran on a *nix system? (I figure *nix users likely won't be using the Windows dialog/window making, etc modules)
I ask because I'm nearly done writing a sane-ish automatic dependency resolution and on the fly syntax checking GNU Makefile for use on *nix systems and with Emacs' flymake-mode. Through some inelegant "parsing" of the output of makedepf90, abuse of the sed command and makefile syntax I have something half decent working with OK abstraction and generality. However, I need to make sure that makedepf90 will ignore any use statements that the compiler will handle for compiler supplied modules. (Otherwise make things that the source file which uses compiler supplied modules can't be built because it doesn't know how to create the corresponding .mod files.)
A little more info for those who are curious: I followed GNU Make's recommended procedure for generating prerequisites automatically which means that there is one dependency file per fortran source file which gets included by GNU Make and automatically updated. This means that when a source file is updated, its dependency information is updated automatically without having to parse all of the source files in a source tree. Furthermore, I followed some of the suggestions at to improve speed, usage and generality from http://mad-scientist.net/make/autodep.html. However, I did violate Paul's 3rd rule of makefiles, to a degree, because I did not want to pollute the source directory with flymake temporary files, mod files and included dependency files. A simple/sane flymake implementation using makefiles requires a Makefile in the CWD and it made sense to me not to mess with this idea.
I will be putting more info up about this on github and the emacs wiki once I am satisfied with my work, hopefully later this afternoon.