From: Daniel Jacobowitz <drow@false.org>
To: Ben Elliston <bje+dated+1087082547.af1bf1@air.net.au>, cagney@gnu.org
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: top-level removal of dejagnu, expect
Date: Wed, 09 Jun 2004 23:26:00 -0000 [thread overview]
Message-ID: <20040609232612.GA19856@nevyn.them.org> (raw)
In-Reply-To: <20040610092223.A1221@mailhub.air.net.au>
On Thu, Jun 10, 2004 at 09:22:23AM +1000, Ben Elliston wrote:
> In preparation for the removal of src/{dejagnu,expect}.
> Okay to commit?
>
> 2004-06-10 Ben Elliston <bje@gnu.org>
>
> * Makefile.def (dejagnu, expect): Remove.
> * Makefile.tpl (EXPECT): Set to 'expect'.
> (RUNTEST): Set to 'runtest'.
> (all-dejagnu): Remove target.
> (configure-expect): Likewise.
> (all-expect): Likewise.
> * Makefile.in: Rebuild.
> * configure.in (host_tools): Remove expect and dejagnu.
> (noconfigdirs): Likewise for all target triples.
> * configure: Rebuild.
> * src-release (do-proto-toplev): Remove kludge for gdb/708.
> (DEJAGNU_SUPPORT_DIRS): Remove.
> (dejagnu.tar.bz2, dejagnu.tar): Likewise.
> (GDBD_SUPPORT_DIRS): Likewise.
> (gdb+dejagnu.tar.bz2, gdb+dejagnu.tar): Likewise.
> (INSIGHTD_SUPPORT_DIRS): Likewise.
> (insight+dejagnu.tar.bz2, insight+dejagnu.tar): Likewise.
This is going to percolate through the repository (modules file should
also be adjusted eventually); you may want to hold off until Andrew has
finished with GDB 6.1.1. Andrew, that should be soon, right?
Every time someone messes with the top level directories, even on HEAD,
GDB snapshots find a way to break.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-09 23:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 23:23 Ben Elliston
2004-06-09 23:26 ` Daniel Jacobowitz [this message]
2004-06-09 23:29 ` Ben Elliston
2004-06-10 14:08 ` Andrew Cagney
2004-06-10 20:10 ` Ben Elliston
2004-06-11 3:44 ` Andrew Cagney
2004-06-11 3:51 ` Ben Elliston
2004-06-11 4:15 ` Andrew Cagney
2004-06-11 4:18 ` Daniel Jacobowitz
2004-06-09 23:40 ` DJ Delorie
2004-06-10 0:15 ` Ben Elliston
2004-06-10 0:38 ` Christopher Faylor
2004-06-10 2:15 ` DJ Delorie
2004-06-10 2:19 ` Ben Elliston
2004-06-10 2:30 ` DJ Delorie
2004-06-10 2:34 ` Ben Elliston
2004-06-10 2:41 ` DJ Delorie
2004-06-10 2:50 ` Ben Elliston
2004-06-10 14:03 ` Andrew Cagney
2004-06-14 20:31 ` Alexandre Oliva
2004-06-10 2:22 ` Ian Lance Taylor
2004-06-10 2:27 ` Ben Elliston
2004-06-10 2:31 ` DJ Delorie
2004-06-14 20:25 ` Alexandre Oliva
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=20040609232612.GA19856@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1087082547.af1bf1@air.net.au \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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