This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files
- From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 31 Aug 2011 23:05:10 +0000
- Subject: [Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files
- Auto-submitted: auto-generated
- References: <bug-49149-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49149
--- Comment #11 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-08-31 23:05:10 UTC ---
On Wed, Aug 31, 2011 at 10:34:46PM +0000, zbeekman at gmail dot com wrote:
> Additionally, if my entire premise is wrong what do you anticipate the use of
> the -M flag will be for? It's not hard to figure out that .o files depend on
> the .f90 files with the same name. I don't need a tool to do that for me, so
> how do you envision -M being used? Not the way listed on the GNUmake online
> documentation?
Given that I consider the -M option to be total irrelevant
for gfortran, I anticipate that the -M option is useless.
In fact there are a boat load of options listed in the GCC
info file, which are irrelevant for gfortran. Many of these
options are historical baggage from when GCC was simply gcc
(ie., a C compiler).
Can you show me a specific passage in the GNU Make documentation
that states -M can be used to generate dependencies for
Fortran USE statements without the actual *.mod being
present?
What to you expect the -M option to do with
program foo
use omp_lib
use iso_c_binding
end program