From: Daniel Jacobowitz <drow@false.org>
To: Olatunji Ruwase <Olatunji.Ruwase@Sun.COM>
Cc: gdb@sourceware.org
Subject: Re: Help with gdb testsuite (lib/gdb.exp)
Date: Wed, 21 Sep 2005 21:48:00 -0000 [thread overview]
Message-ID: <20050921214801.GA18635@nevyn.them.org> (raw)
In-Reply-To: <4331D3DE.7090700@Sun.COM>
On Wed, Sep 21, 2005 at 02:42:54PM -0700, Olatunji Ruwase wrote:
> Thanks for your response. I found out that release versions I quoted in
> my initial email were wrong, sorry about that :(.
> runtest was picking up an older version of expect and tcl.
>
> % runtest -V
> WARNING: Couldn't find the global config file.
> Expect version is 5.25.0
> Tcl version is 8.0
> Framework version is 1.4.4
>
> The simple test you prescribed worked on tcl version 8.4 but not on 8.0,
> i.e newlines remain in $b.
> Making runtest use the newer releases solved the problem.
There you go; thanks for confirming. That TCL version is six years
old, so I don't feel really obliged to support it.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-09-21 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 18:35 Olatunji Ruwase
2005-09-21 18:53 ` Daniel Jacobowitz
2005-09-21 21:43 ` Olatunji Ruwase
2005-09-21 21:48 ` Daniel Jacobowitz [this message]
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=20050921214801.GA18635@nevyn.them.org \
--to=drow@false.org \
--cc=Olatunji.Ruwase@Sun.COM \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).