From: Andreas Jaeger <aj@suse.de>
To: gcc@gcc.gnu.org
Subject: problem running the testsuite
Date: Tue, 20 May 2003 13:32:00 -0000 [thread overview]
Message-ID: <hou1bpeojo.fsf@byrd.suse.de> (raw)
Running the testsuite on x86-64-linux-gnu I got today for the first
time the following failure:
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /cvs/gcc/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /cvs/gcc/gcc/testsuite/g77.dg/bprob/bprob.exp ...
Running /cvs/gcc/gcc/testsuite/g77.dg/dg.exp ...
ERROR: tcl error sourcing /cvs/gcc/gcc/testsuite/g77.dg/dg.exp.
ERROR: couldn't compile regular expression pattern: parentheses () not balanced
while executing
"regexp "$pattern" $lower"
(procedure "search_for" line 5)
invoked from within
"search_for $test "for*(""
(procedure "gcc-dg-runtest" line 14)
invoked from within
"gcc-dg-runtest $testcases ${default-extra-flags}"
(procedure "g77-dg-runtest" line 2)
invoked from within
"g77-dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/*.f]] \
$DEFAULT_FFLAGS"
(file "/cvs/gcc/gcc/testsuite/g77.dg/dg.exp" line 32)
invoked from within
"source /cvs/gcc/gcc/testsuite/g77.dg/dg.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source /cvs/gcc/gcc/testsuite/g77.dg/dg.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Running /cvs/gcc/gcc/testsuite/g77.dg/gcov/gcov.exp ...
I run "make -k check" and have set in the environment
RUNTESTFLAGS="--target_board 'unix{-m32,}'" so that both 32-bit and
64-bit tests are run. This worked a few days ago (last time I
bootstrapped),
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
reply other threads:[~2003-05-20 13:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=hou1bpeojo.fsf@byrd.suse.de \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.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).