This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/47720] problems with makefile dependency generation using -M
- From: "kristopher.kuhlman at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 25 May 2011 19:37:03 +0000
- Subject: [Bug fortran/47720] problems with makefile dependency generation using -M
- Auto-submitted: auto-generated
- References: <bug-47720-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47720
--- Comment #2 from Kris <kristopher.kuhlman at gmail dot com> 2011-05-25 19:36:48 UTC ---
(In reply to comment #1)
> May I ask what version of gfortran this is? (Trunk build of gfortran from
> yesterday is a bit ambiguous)
I was using a build of gfortran from CVS 2/12/2011.
> The reason I ask is that I am not getting as far as you. on gfortran 4.6.0 if
> have a program which uses two modules and dependency listing I get is myprog.0:
> myprog.f90 which is less than helpful.
Using a more recent trunk build (sometime last week), I still get what I
originally posted.
$ gfortran-4.7 -cpp -M makegen?.f90
makegen1.o constants.mod: makegen1.f90
makegen2.o utility.mod: makegen2.f90 constants.mod constants.mod \
constants.mod
If it is considered to be ok that there is all this duplication, then I guess I
don't have a problem. Maybe the documentation for this feature could be
cleared up to mention this too?