From: Daniel Jacobowitz <drow@mvista.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Which dejagnu version do we require?
Date: Fri, 31 Jan 2003 10:25:00 -0000 [thread overview]
Message-ID: <20030131035759.GA12470@nevyn.them.org> (raw)
In-Reply-To: <Pine.BSF.4.51.0301310311140.1541@acrux.dbai.tuwien.ac.at>
On Fri, Jan 31, 2003 at 03:14:29AM +0100, Gerald Pfeifer wrote:
> I just tried running the testsuite with dejagnu-1.4.2 and got the
> following error:
>
> Using /sw/test/gcc/cvs/libstdc++-v3/testsuite/config/default.exp as
> tool-and-tar
> get-specific interface file.
> Running /sw/test/gcc/cvs/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp ...
> ERROR: tcl error sourcing /sw/test/gcc/cvs/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp.
> ERROR: couldn't compile regular expression pattern: nested *?+
> while executing "regsub "^$srcdir/?" $prog "" name"
> (procedure "dg-test" line 37)
> invoked from within "dg-test $testcase $flags ${default-extra-flags}"
> (procedure "dg-runtest" line 10)
> invoked from within "dg-runtest [libstdc++-v3-list-sourcefiles] "" $DEFAULT_CXXFLAGS"
> (file "/sw/test/gcc/cvs/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp" line33)
> invoked from within "source /sw/test/gcc/cvs/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp"
> ("uplevel" body line 1)
> invoked from within "uplevel #0 source /sw/test/gcc/cvs/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp"
> invoked from within "catch "uplevel #0 source $test_file_name""
>
> Does this mean my setup is somehow hosed or that we now require
> dejagnu-1.4.3?
>
> (If the latter, I'm going to update our documentation, but I wonder why
> nobody else has done this yet...)
This is more likely to be a sensitivity to the version of TCL than the
version of DejaGNU.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-31 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 5:31 Gerald Pfeifer
2003-01-31 10:25 ` Daniel Jacobowitz [this message]
2003-02-01 17:36 ` Gerald Pfeifer
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=20030131035759.GA12470@nevyn.them.org \
--to=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).