From: hjl@lucon.org (H.J. Lu)
To: manfred@s-direktnet.de, Manfred.Hollstein@ks.sel.alcatel.de
Cc: egcs@cygnus.com
Subject: Re: Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)
Date: Tue, 29 Sep 1998 13:08:00 -0000 [thread overview]
Message-ID: <m0zO619-000395C@ocean.lucon.org> (raw)
In-Reply-To: <13840.36399.499908.704222@slsvhmt>
> But, I agree with H.J., it would be fine if more people were testing
> libg++ from time to time. For instance, the current mainline sources
> look pretty much OK without libg++, but with libg++ "make check" fails
> for hppa1.1-hp-hpux10.20, m68k-motorola-sysv and m88k-motorola-sysv3.
> Perhaps it would also be helpful if we'd extend the test_summary script
> to report if "configure"d directories have been found in the tree, but
> the particular *.log files are missing. Currently if libg++ fails, no
> results are posted for libg++ and nobody knows there's a problem :-(
>
FWIW, the current egcs in CVS still miscompiles libg++ on
Linux/x86. I may not have time to look into it before the
end of October.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-09-29 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-26 17:40 Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)testsuite on i586-pc-linux-gnulibc1 David Rees
1998-09-27 11:51 ` Craig Burley
1998-09-27 17:34 ` Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental) H.J. Lu
1998-09-28 3:19 ` Jeffrey A Law
1998-09-29 10:10 ` Manfred Hollstein
1998-09-29 13:08 ` H.J. Lu [this message]
1998-09-29 22:26 ` Jeffrey A Law
1998-09-27 20:41 ` libf2c build problems? Was: Results for egcs-2.92.11 19980921 (gcc2 ss-980609 experimental) testsuite on i586-pc-linux-gnulibc1 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=m0zO619-000395C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=manfred@s-direktnet.de \
/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).