This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49149

--- Comment #8 from Zaak <zbeekman at gmail dot com> 2011-08-31 22:27:40 UTC ---
(In reply to comment #7)
> On Wed, Aug 31, 2011 at 10:01:06PM +0000, zbeekman at gmail dot com wrote:
> > 
> > I hope you are less confused now.
> > 
> 
> I'm not confused.  I do, however, use the grey matter
> between my ears to write my Makefiles.
> 
> gfortran requires that the *.mod are present to
> parse your code.  Sorry if you cannot deal with 
> that fact.

I didn't mean any insult, I am not trying to troll or start a flame war. I'm
sorry if I offended you in any way. I would appreciate you telling me why you
think my makefile is wrong rather than just insulting me. Did you read the link
to the GNUmake manpage? Did you try executing the command outside of the
makefile?

The whole point of having dependency generation capabilities is to do EXACTLY
what I'm trying to do. The .mod files are the difficulty resolving Fortran
dependencies and I don't see what the use of a tool to resolve dependencies is,
if you need to already have those dependencies resolved apriori to use the
tool. If you can show me how to write a makefile with pattern rules that will
automatically resolve dependencies and uses only brief, terse, pattern rules
you will forever be my hero.

How would you write a makefile to automatically build fortran codes, and
resolve their dependencies without explicitly hand coding the dependencies?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]