Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/testsuite/ada] re-implement make clean & distclean
Date: Sun, 31 Dec 2006 13:12:00 -0000	[thread overview]
Message-ID: <200612311312.kBVDCA3B000981@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20061231100755.GQ3640@adacore.com> (message from Joel Brobecker 	on Sun, 31 Dec 2006 14:07:55 +0400)

> Date: Sun, 31 Dec 2006 14:07:55 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Hello,
> 
> The current implementation for make clean requires us that we update
> the EXECUTABLES list each time we add a new testcase. It was a vague
> copy/paste of some code I probably found in one of the nearby Makefiles...
> It was causing me a bit of grief that certain files would not be deleted
> when I did a "make clean", in particular the executables produced by
> gnatmake. I decided to replace this with an approach we have been using
> with great success in our own testsuite for years...
> 
> 2006-12-31  Joel Brobecker  <brobecker@adacore.com>
> 
>         * gdb.ada/Makefile.in (EXECUTABLES): Delete.
>         (MISCELLANEOUS): Delete.
>         (clean): Re-implement.
>         (mostlyclean): Likewise.
> 
> Tested on my x86-linux laptop.  Any objection?

Hmm, seems a bit scary to me.  If I read this correctly, a file named
NOTES would be wiped isn't it?  I'm using a seperate object dir, so I
probably won't care, but others might...


  reply	other threads:[~2006-12-31 13:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 10:08 Joel Brobecker
2006-12-31 13:12 ` Mark Kettenis [this message]
2006-12-31 14:31   ` Joel Brobecker
2006-12-31 14:54     ` Jim Blandy
2006-12-31 15:19     ` Daniel Jacobowitz
2006-12-31 15:27       ` Joel Brobecker
2006-12-31 18:05         ` Daniel Jacobowitz
2007-01-01 14:14           ` Joel Brobecker

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=200612311312.kBVDCA3B000981@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.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