From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: aoliva@redhat.com, cagney@gnu.org
Cc: binutils@sources.redhat.com,
bje+dated+1087798498.8ed310@air.net.au, brobecker@gnat.com,
gcc@gcc.gnu.org, gdb@sources.redhat.com, Joe.Buck@synopsys.com,
zack@codesourcery.com
Subject: Re: PROPOSAL: removing src/expect
Date: Wed, 16 Jun 2004 15:31:00 -0000 [thread overview]
Message-ID: <20040616153100.D08E04B104@berman.michael-chastain.com> (raw)
Andrew C writes:
> Independent of what happens to this thread, I think GDB (and GCC?)
> should clarify their test procedures so that they don't direct the
> developer towards src/expect/.
I agree.
I guess it's my job to write some doco on "how to run the gdb test
suite", and I'll include the steps for downloading tcl + expect +
dejagnu from their public release locations and then building the
things. I've added this to my to-do list.
One thing I need is a Cygwin + gdb testsuite volunteer.
Anybody out there?
Michael C
next reply other threads:[~2004-06-16 15:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 15:31 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 3:24 Michael Elizabeth Chastain
2004-06-17 17:30 ` Christopher Faylor
2004-06-15 4:37 Michael Elizabeth Chastain
2004-06-15 4:15 Ben Elliston
2004-06-15 20:35 ` Alexandre Oliva
2004-06-15 21:32 ` Zack Weinberg
2004-06-15 22:24 ` Alexandre Oliva
2004-06-15 22:29 ` Zack Weinberg
2004-06-15 22:56 ` Daniel Jacobowitz
2004-06-15 23:07 ` Andrew Cagney
2004-06-15 23:40 ` Andreas Schwab
2004-06-15 22:50 ` Joe Buck
2004-06-16 3:34 ` Alexandre Oliva
2004-06-16 3:35 ` Ben Elliston
2004-06-16 6:11 ` Joel Brobecker
2004-06-16 6:15 ` Ben Elliston
2004-06-16 7:08 ` Alexandre Oliva
2004-06-16 13:46 ` Andrew Cagney
2004-06-16 16:30 ` Joe Buck
2004-06-16 19:53 ` Alexandre Oliva
2004-06-16 22:48 ` Ben Elliston
2004-06-16 16:27 ` Joe Buck
2004-06-15 22:43 ` Ben Elliston
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=20040616153100.D08E04B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=Joe.Buck@synopsys.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1087798498.8ed310@air.net.au \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=zack@codesourcery.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