Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 17:16:00 -0000	[thread overview]
Message-ID: <m37i37u9p7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e394668d0903020831v1af6c39dpa7731b293829a0ae@mail.gmail.com> (Doug Evans's message of "Mon\, 2 Mar 2009 08\:31\:08 -0800")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> I don't disagree, but it seems like .deps should be cleared out with a
Doug> "make clean" regardless.  After a configure the build directory is
Doug> clean and .deps is empty (or doesn't exist).  For consistency sake, it
Doug> makes sense to have the same after a "make clean".

Yeah, I agree.  In Automake we had a set of rules: if "configure" made
it, "distclean" deletes it; if "make" made it, "clean" deletes it; and
if the maintainer made it, "maintainer-clean" deletes it.

I think I got a little confused here because (IIRC) Automake arranges
for configure to make initial .Po files.  But, that's because Automake
has to work in a much less friendly environment -- it is an
implementation detail.

I still think we want to also fix this in libcpp, though, because I
think it is reasonable to use this style of dependency management, to
rename a source file, and to expect a plain "make" to just work.

Tom


      reply	other threads:[~2009-03-02 17:16 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
2009-03-02 16:31       ` Doug Evans
2009-03-02 17:16         ` Tom Tromey [this message]

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=m37i37u9p7.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