From: "J. Kean Johnston" <jkj@sco.com>
To: EGCS Mailing List <egcs@cygnus.com>
Subject: 971201 SCO Open Server results (ELF)
Date: Tue, 02 Dec 1997 22:54:00 -0000 [thread overview]
Message-ID: <19971202171512.09792@sco.com> (raw)
Summary of "make check" for EGCS 971201 on SCO Open Server 5.0.4 in the
default (ELF) mode:
Test Run By jkj on Tue Dec 2 16:46:25 1997
Native configuration is i386-pc-sco3.2v5.0
=== libio Summary ===
# of expected passes 40
Test Run By jkj on Tue Dec 2 16:46:56 1997
Native configuration is i386-pc-sco3.2v5.0
=== libstdc++ Summary ===
# of expected passes 30
Test Run By jkj on Tue Dec 2 16:47:26 1997
Native configuration is i386-pc-sco3.2v5.0
=== gcc Summary ===
# of expected passes 4883
# of expected failures 5
# of unsupported tests 7
/u/tmp/egcs-971201/gcc/xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
Test Run By jkj on Tue Dec 2 17:00:02 1997
Native configuration is i386-pc-sco3.2v5.0
=== g++ Summary ===
# of expected passes 3398
# of unexpected failures 1
# of unexpected successes 3
# of expected failures 81
# of untested testcases 6
/u/tmp/egcs-971201/gcc/testsuite/../xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
FAIL: g++.law/profile1.C (test for excess errors)
Executing on host: /u/tmp/egcs-971201/gcc/testsuite/../xgcc -B/u/tmp/egcs-971201/gcc/testsuite/../ /u/tmp/egcs-971201/gcc/testsuite/g++.old-deja/g++.law/profile1.C -pg -I/u/tmp/egcs-971201/libio -I/u/tmp/egcs-971201/libraries/libio -I/u/tmp/egcs-971201/libstdc++ -I/u/tmp/egcs-971201/libstdc++/stl -I/u/tmp/egcs-971201/gcc/testsuite/../include -lstdc++ -L/u/tmp/egcs-971201/libraries//libstdc++ -L/u/tmp/egcs-971201/libraries//libiberty -lm -o /tmp/a.out
compiler exited with status 1
output is:
gcrt.o: fatal error: cannot open file for reading
collect2: ld returned 1 exit status
This is, I guess, an "expected" failure. But where, oh where, is gcrt.o
supposed to come from?
JKJ.
reply other threads:[~1997-12-02 22:54 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=19971202171512.09792@sco.com \
--to=jkj@sco.com \
--cc=egcs@cygnus.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).