From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Makefile.in (clean): rm -f $(DEPDIR)/*.
Date: Mon, 02 Mar 2009 01:06:00 -0000 [thread overview]
Message-ID: <m3zlg4wx6f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e394668d0903011658s2d5c4242s8e681ca09d804b7f@mail.gmail.com> (Doug Evans's message of "Sun\, 1 Mar 2009 16\:58\:28 -0800")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> make: *** No rule to make target `../../../src/gdb/signals/signals.c',
Doug> needed by `signals.o'. Stop.
Doug> This is because signals.c has moved, but .deps/mumble still refers to
Doug> the old location.
Thanks, I see.
Your patch is ok.
It is interesting that I have never run across this particular failure
before. This style of dependency tracking has been in use for a long
time...
I think the underlying problem is a bug in gcc. I think -MP ought to
emit a dummy target for the primary source file as well. I made a
note to fix this in libcpp.
Tom
next prev parent reply other threads:[~2009-03-02 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 0:10 Doug Evans
2009-03-02 0:55 ` Tom Tromey
2009-03-02 0:58 ` Doug Evans
2009-03-02 1:06 ` Tom Tromey [this message]
2009-03-02 16:31 ` Doug Evans
2009-03-02 17:16 ` Tom Tromey
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=m3zlg4wx6f.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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