From: Andreas Jaeger <aj@suse.de>
To: gdb@sources.redhat.com
Subject: Testsuite status/proper configure?
Date: Sun, 08 Jul 2001 07:48:00 -0000 [thread overview]
Message-ID: <u84rsnjx4t.fsf@gromit.moeb> (raw)
I'm a little bit puzzled. I checked out the full sourceware source
tree, run
/cvs/sourceware-src/configure --prefix=/opt/gdb --disable-shared --enable-threads \
--with-gnu-as --with-gnu-ld \
--enable-build-warnings --disable-nls --disable-tui --disable-gdbtk
and then make all-gdb to build gdb on i686-linux-gnu (with glibc 2.2.2).
Running the testsuite with make check-gdb gave me lots of failures:
=== gdb Summary ===
# of expected passes 7515
# of unexpected failures 145
# of unexpected successes 32
# of expected failures 192
# of unresolved testcases 120
/builds/sourceware-src/build-gdb/gdb/testsuite/../../gdb/gdb version 2001-07-08-cvs -nx
Have I done something wrong? Is there a better method for building
only gdb from the complete sourceware tree?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2001-07-08 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 7:48 Andreas Jaeger [this message]
2001-07-08 9:49 Michael Elizabeth Chastain
2001-07-08 10:49 ` Andreas Jaeger
2001-07-12 12:50 ` Mark Kettenis
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=u84rsnjx4t.fsf@gromit.moeb \
--to=aj@suse.de \
--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