From: Kevin Buettner <kevinb@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Some "distclean" fixes in gdb
Date: Tue, 1 Mar 2022 13:04:57 -0700 [thread overview]
Message-ID: <20220301130457.13d8467f@f35-zws-1> (raw)
In-Reply-To: <20220228003358.487744-1-tom@tromey.com>
On Sun, 27 Feb 2022 17:33:58 -0700
Tom Tromey <tom@tromey.com> wrote:
> PR build/12440 points out that "make distclean" is broken in gdb.
> Most of the breakage comes from other projects in the tree, but we can
> fix some of the issues, which is what this patch does.
>
> Note that the yacc output files, like c-exp.c, are left alone. In a
> source distribution, these are included in the tarball, and if the
> user builds in-tree, we would not want to remove them.
>
> While that seems a bit obscure, it seems to me that "distclean" is
> only really useful for in-tree builds anyway -- out-of-tree I simply
> delete the entire build directory and start over.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=12440
Wow, that's an old bug.
Regardless, this seems reasonable to me.
Kevin
prev parent reply other threads:[~2022-03-01 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 0:33 Tom Tromey
2022-03-01 20:04 ` Kevin Buettner [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=20220301130457.13d8467f@f35-zws-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).