Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ben Elliston <bje+dated+1087771427.e12be6@air.net.au>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: PROPOSAL: removing src/expect
Date: Tue, 15 Jun 2004 22:43:00 -0000	[thread overview]
Message-ID: <20040616084342.A24438@mailhub.air.net.au> (raw)
In-Reply-To: <orpt808sqv.fsf@free.redhat.lsd.ic.unicamp.br>; from aoliva@redhat.com on Tue, Jun 15, 2004 at 05:35:04PM -0300

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

> Err...  Yes, for the same reasons as dejagnu.  It's not bundled with
> most of the OSs I used to test, and being able to build expect along
> with tcl/tk/etc that were built for GDB/Insight, and dejagnu, that
> requires it, was quite handy.  Sure it's old, but it doesn't hurt as
> long as it works, no?  And it's not like you're required to check it
> out.  I'd rather just leave it there, like dejagnu.

In some instances, it is hurting.  A default "src" tree will build and
then use the in-tree expect when running any of the testsuites.  There
have been problems reported that may well have been fixed in the
latest versions of Expect.  However, we're not taking any advantage of
improvements or bug fixes being made by the Expect maintainer(s), thus
creating more hassles and work for ourselves.

Anyway, it's clear that I'm swimming upstream, so I'll let this thread
drop now.

Ben

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-06-15 22:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-06-15  4:37 Michael Elizabeth Chastain
2004-06-16 15:31 Michael Elizabeth Chastain
2004-06-17  3:24 Michael Elizabeth Chastain
2004-06-17 17:30 ` Christopher Faylor

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=20040616084342.A24438@mailhub.air.net.au \
    --to=bje+dated+1087771427.e12be6@air.net.au \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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