From: Robert Lipe <robertl@dgii.com>
To: egcs@cygnus.com
Subject: GCC 971031 on OpenServer
Date: Sat, 01 Nov 1997 20:49:00 -0000 [thread overview]
Message-ID: <19971101224835.30144@dgii.com> (raw)
Jeff's dwarf2out.c patch applied. Top level make bootstrap-lean
to build it.
--target=i586-pc-sco3.2v5.0.4
For GCC, Both ELF and COFF fail minimally and identically.
FAIL: gcov failed: couldn't execute "./gcov": no such file or directory
=== gcc Summary ===
# of expected passes 4882
# of unexpected failures 1
# of expected failures 5
# of unsupported tests 7
./negcs version egcs-2.90.15 971031 (gcc2-970802 experimental)
next reply other threads:[~1997-11-01 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-01 20:49 Robert Lipe [this message]
1997-11-02 12:48 ` disturbing g++ 971031 results. defer-pop to blame? Robert Lipe
1997-11-02 19:06 ` Jeffrey A Law
1997-11-02 20:47 ` Robert Lipe
1997-11-02 22:44 ` Jeffrey A Law
1997-11-02 23:32 ` Robert Lipe
1997-11-03 2:06 ` Jeffrey A Law
1997-11-03 2:06 ` Robert Lipe
1997-11-03 1:51 ` Jeffrey A Law
1997-11-03 3:21 ` Andreas Schwab
1997-11-03 9:43 ` Robert Lipe
[not found] ` <16810.878541954.cygnus.egcs@hurl.cygnus.com>
1997-11-03 2:28 ` Jason Merrill
1997-11-03 9:43 ` disturbing g++ 971031 results. defer-pop not to blame Robert Lipe
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=19971101224835.30144@dgii.com \
--to=robertl@dgii.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).