Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb@sources.redhat.com, me@cgf.cx
Subject: Re: [Gdb] removing src/dejagnu, src/expect
Date: Tue, 08 Jun 2004 21:29:00 -0000	[thread overview]
Message-ID: <20040608212940.DC94B4B104@berman.michael-chastain.com> (raw)

> The problem with that approach is that you can't necessarily fix all of
> the problems can you?  In particular, as you noted in the gcc mailing
> list, Cygwin could be a problem.

You're right; I can't fix the problems.

It would help if someone would post cygwin gdb results to gdb-testers
so that we know if gdb even builds and the test suite runs.  The last
cygwin results were from Raoul Gough on 2003-04-28.

I've gotten into a mood where if gdb-testers doesn't contain any recent
results for a platform, then I don't care too much if that platform
breaks.  Which is actually a bad mood because that includes major
platforms like solaris and cygwin.

Also please note that the decision to remove expect+dejagnu came from
the Gcc Summit and was announced by Ben Elliston, who's going to do
the actual removal on 2004-06-11, unless someone objects.

Michael C


             reply	other threads:[~2004-06-08 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 21:29 Michael Elizabeth Chastain [this message]
2004-06-09  0:54 ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09  2:24 Michael Elizabeth Chastain
     [not found] <1086697608.21986.ezmlm@sources.redhat.com>
2004-06-08 17:35 ` Jim Ingham
2004-06-07 21:58 Michael Elizabeth Chastain
2004-06-08 20:57 ` Christopher Faylor
     [not found] <1086598259.8126.ezmlm@sources.redhat.com>
2004-06-07 21:37 ` Jim Ingham
     [not found] <20040605143942.E37E74B104@berman.michael-chastain.com>
2004-06-05 16:13 ` Daniel Jacobowitz

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=20040608212940.DC94B4B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb@sources.redhat.com \
    --cc=me@cgf.cx \
    /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