From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: msnyder@vmware.com
Cc: brobecker@adacore.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfa] make clean should remove observe.h and observer.inc
Date: Thu, 24 Feb 2011 19:04:00 -0000 [thread overview]
Message-ID: <201102241900.p1OJ0TX4029334@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4D66A320.6040007@vmware.com> (message from Michael Snyder on Thu, 24 Feb 2011 10:27:44 -0800)
> Date: Thu, 24 Feb 2011 10:27:44 -0800
> From: Michael Snyder <msnyder@vmware.com>
>
> Joel Brobecker wrote:
> >> That brings up another question. What about <lang>-exp.c? Technically
> >> they are generated files. Should make clean remove them?
> >
> > I would say no - we check them in so to allow users to build
> > GDB without requiring bison/flex. It would be problematic for
> > them if they disappeared at a simple "make clean".
> >
>
> We don't check them in -- they're not in cvs. We add them to the tar
> file when we make a release.
>
> OK, though, how about "make distclean"?
Same for "make distclean"; "make distclean" should restore the source
tree into the state it was in just after untarring the GDB release
tarball.
next prev parent reply other threads:[~2011-02-24 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:56 Michael Snyder
2011-02-23 21:44 ` Michael Snyder
2011-02-24 7:20 ` Jan Kratochvil
2011-02-24 15:46 ` Tom Tromey
2011-02-24 18:25 ` Michael Snyder
2011-02-24 18:27 ` Joel Brobecker
2011-02-24 18:39 ` Michael Snyder
2011-02-24 18:57 ` Tom Tromey
2011-02-24 19:04 ` Mark Kettenis [this message]
2011-02-24 19:01 ` Mark Kettenis
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=201102241900.p1OJ0TX4029334@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=tromey@redhat.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