https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81651
Bug ID: 81651
Summary: Enhancement request: have f951 print out fully
qualified module file name
Product: gcc
Version: 6.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: hbl3973 at gmail dot com
Target Milestone: ---
Working with cmake to build our local source tree, I ran into the f951 message
that it received an unexpected EOF reading fort_func_mod.mod. Our cmake
configuration invokes the -J flag to place modules in a central directory.
After several days of digging through Xpert Xchange, compiler -v output, etc.,
I found that there was a stray fort_func_mod.mod file in the source tree that
had been created by an Intel compiler in the same directory as the
fort_func_mod.f90 file. While the documentation for the -J flag does say that
gfortran looks in the current directory, this is ambiguous as cmake uses the
toplevel directory for all its actions and compiles and links with fully
qualified paths to a subdirectory in the source or build tree.
Bottom line: had f951 printed out a fully qualified module name in its error
message, the problem would have been obvious and fixed immediately.
