public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files
Date: Thu, 01 Sep 2011 01:14:00 -0000	[thread overview]
Message-ID: <bug-49149-4-GQdpeoLKNE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49149-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Zaak <zbeekman at gmail dot com> 2011-09-01 01:14:40 UTC ---

> 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?

Bullet number 7 in the what's new in gfortran section for the current stable
release, 4.6.0: http://gcc.gnu.org/wiki/GFortran#GCC4.6

' Support the generation of Makefile dependencies via the `-M...` flags of GCC;
you may need to specify additionally the -cpp option. The dependencies take
modules, Fortran's include, and CPP's #include into account. Note: Using -M for
the module path is no longer supported, use -J instead.'

It seems that this is a new feature and the documentation lags the
implementation. Being a new feature I thought it was important to report what
appears to me to be an important new bug (if I am interpreting the above
statement correctly). Note also that Intel has recently added this capability
to their Fortran compiler and they too have (different) bugs.


  parent reply	other threads:[~2011-09-01  1:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 20:09 [Bug fortran/49149] New: " zbeekman at gmail dot com
2011-05-24 22:02 ` [Bug fortran/49149] " kargl at gcc dot gnu.org
2011-07-24 19:06 ` dfranke at gcc dot gnu.org
2011-08-31 20:06 ` zbeekman at gmail dot com
2011-08-31 20:24 ` zbeekman at gmail dot com
2011-08-31 21:06 ` kargl at gcc dot gnu.org
2011-08-31 22:18 ` zbeekman at gmail dot com
2011-08-31 22:28 ` sgk at troutmask dot apl.washington.edu
2011-08-31 22:46 ` zbeekman at gmail dot com
2011-08-31 23:05 ` zbeekman at gmail dot com
2011-08-31 23:21 ` sgk at troutmask dot apl.washington.edu
2011-09-01  1:14 ` zbeekman at gmail dot com [this message]
2011-09-01  1:28 ` zbeekman at gmail dot com
2011-09-03 14:47 ` zbeekman at gmail dot com
2011-11-07 22:52 ` fxcoudert at gcc dot gnu.org
2015-03-03 21:09 ` zbeekman at gmail dot com
2015-03-03 21:20 ` zbeekman at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-49149-4-GQdpeoLKNE@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).