public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/28810] gcc -MD -MP doesn't add phony rule for source file
Date: Tue, 26 Dec 2006 00:24:00 -0000	[thread overview]
Message-ID: <20061226002424.31285.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28810-6236@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from tromey at gcc dot gnu dot org  2006-12-26 00:24 -------
I think the rationale here is just that, if -MP added the main source
file as a phony target, then 'make' would not do anything at all if the
main file was missing.  But, that result seems wrong -- for this to trigger
your Makefile must still have some dependency on the old .o file.  So,
presumably the dependency ought to mean something, and not just be
silently ignored.

How is it that your Makefile has a dependency on the old .o even
when the main file name has changed?  Isn't that a Makefile bug?


-- 

tromey at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-12-26 00:24:20
               date|                            |


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


  parent reply	other threads:[~2006-12-26  0:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 20:21 [Bug preprocessor/28810] New: " carlton at bactrian dot org
2006-08-22 20:29 ` [Bug preprocessor/28810] " pinskia at gcc dot gnu dot org
2006-12-26  0:24 ` tromey at gcc dot gnu dot org [this message]
2006-12-26  3:24 ` carlton at bactrian dot org
2007-01-08  2:22 ` tromey at gcc dot gnu dot org

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=20061226002424.31285.qmail@sourceware.org \
    --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).