From: "Pinwu Xu" <pinwu_xu@hotmail.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: 1.0 release stopped compiling in libg++
Date: Thu, 04 Dec 1997 20:26:00 -0000 [thread overview]
Message-ID: <19971205034734.14209.qmail@hotmail.com> (raw)
> In message < 19971204153800.27686.qmail@hotmail.com >you write:
> > I tried to compile on Slackware system, gcc2.7.2.3, libc5.4.39,
> > libpthread 0.6, binutils 2.8.0.15 (the publically newest one),
> > ld.so1.9.5. Grabbed libg++2.8.0.b6.3 from HJu's private ftp dir.
>HU would have to comment on this. Could be with with_gxx_include_dir
>problem.
Sorry for my previous post. After I applied HJLu's patch
stated in README.libg++, reran configure, the compilation
finished! I'll list the testing result later.
> > BTW, what's the disk requirement? I got about 160M after
install-
> > ing the source, will this be enough to run "make bootstrap"
>I actually don't know.
>
>It looks like my x86-linux is 100M with a "make bootstrap" of the
entire
>distribution.
>
>So 160M should be OK.
Well, 160M is barely enough.
>
>There's some targets for continueing a build; wander through the
toplevel
>Makefile.in looking for bootstrap, bootstrap2, bootstrap3 and similar
>targets.
"make -k check" gives:
=== g++ Summary ===
# of expected passes 2943
# of unexpected failures 457
# of unexpected successes 1
# of expected failures 82
# of untested testcases 6
/home/pxu/tmp/objdir/gcc/testsuite/../xgcc version egcs-2.90.21 971202
(egcs-1.00 release)
=== g77 Summary ===
# of expected passes 130
# of unexpected failures 2
/home/pxu/tmp/objdir/gcc/g77 version egcs-2.90.21 971202 (egcs-1.00
release)
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-loops
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops
=== gcc Summary ===
# of expected passes 4883
# of expected failures 5
# of unsupported tests 7
/home/pxu/tmp/objdir/gcc/xgcc version egcs-2.90.21 971202 (egcs-1.00
release)
XFAIL: gcc.c-torture/compile/961203-1.c
XFAIL: gcc.failure/940409-1.c, -O0
XFAIL: gcc.failure/940409-1.c, -O1
XFAIL: gcc.failure/940409-1.c, -O2
XFAIL: gcc.failure/940409-1.c, -O2 -fomit-frame-pointer
-finline-functions
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
The "make -k check" ended with some error (I don't have the error
message now :-( ). But at least the whole egcs compiles!
Thanks for all who replied.
Pinwu
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
next reply other threads:[~1997-12-04 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-04 20:26 Pinwu Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-04 10:12 Pinwu Xu
1997-12-04 13:27 ` Jeffrey A Law
1997-12-04 14:41 ` H.J. Lu
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=19971205034734.14209.qmail@hotmail.com \
--to=pinwu_xu@hotmail.com \
--cc=egcs@cygnus.com \
--cc=law@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).