[Bug fortran/42607] add information about how to compile a module
------- Comment #7 from kargl at gcc dot gnu dot org 2010-04-04 20:28 -------
(In reply to comment #5)
> (In reply to comment #1)
> > > should -c explain how a .mod file is created?
> >
> > IMHO, the answer is a resounding 'no.' Adding such information
> > would simply add unneeded clutter to the manual, and should be
> > an insult to anyone that uses Fortran.
>
> Not documenting the semantics of module files anywhere is a sure way for build
> tools like Automake to never get decent support for building Fortran. As it is
> now, the user needs to fake dependencies manually to make up for this missing
> information. (Where to put the information is another question altogether.)
I don't use automake, so I really don't care what it does or does
not do.
> > Also, the Fortran standard does not require that a .mod be created,
>
> The Fortran standard is irrelevant for this question. Users want 'make clean'
> to remove cruft that 'make' created, and you don't provide a 'gfortran --clean'
> to keep information about .mod files under the hood either.
>
The Fortran standard is the only thing that matters.
'make clean' does the right thing for me. Of course,
I know how to write a Makefile without depending on
the whim (yes, I wrote whim) of the automake developers.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42607
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
Reply to: