From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb@sources.redhat.com>
Subject: "make check" doesn't work on RedHat 9?
Date: Fri, 09 May 2003 18:07:00 -0000 [thread overview]
Message-ID: <20030509110706.A4628@lucon.org> (raw)
Does "make check" work RedHat 9? I got
Running /export/gnu/src/gdb/gdb/gdb/testsuite/gdb.base/printcmds.exp ...
ERROR: (DejaGnu) proc "setup_kfail gdb/538 *-*-*" does not exist.
The error code is NONE
The info on the error is:
close: spawn id exp6 not open
while executing
"close -i exp6"
invoked from within
RedHat 9 has dejagnu 1.4.2. I was told dejagnu 1.4.3 and cvs doesn't
work with binutils:
http://sources.redhat.com/ml/binutils/2003-05/msg00248.html
H.J.
next reply other threads:[~2003-05-09 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 18:07 H. J. Lu [this message]
2003-05-09 18:16 ` Elena Zannoni
2003-05-09 18:18 ` Daniel Jacobowitz
2003-05-09 18:32 ` H. J. Lu
2003-05-09 19:06 ` PATCH: Fix dejagnu H. J. Lu
2003-05-09 18:12 "make check" doesn't work on RedHat 9? Michael Elizabeth Chastain
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=20030509110706.A4628@lucon.org \
--to=hjl@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).