From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Re: Here are the g++ test results
Date: Wed, 27 Aug 1997 05:21:33 -0000 [thread overview]
Message-ID: <m0x3ZBA-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970827052133.LvmNOz0_ksPpJfQvwAMOxqFe98SWl6vfiseDAShWvrs@z> (raw)
In-Reply-To: Here are the g++ test results
In message <Pine.PMDF.3.91.970826184842.538979005A-100000@MPS.OHIO-STATE.EDU>
you write:
> # of expected passes 3192
> # of unexpected failures 56
> # of unexpected successes 2
> # of expected failures 95
> # of untested testcases 10
>
> g++.log and gcc.log are available for interested parties by anon. ftp at
> niobium.mps.ohio-state.edu (gzipped). If any other info is needed please
> let me know.
Thanks. I think I see the problem.
It appears that you're picking up include files from /usr/include/g++,
and for whatever reason they are not compatable with the current
compiler.
I believe this is a bug in the dejagnu framework since it should
be providing appropriate overriding -I arguments so that you pick
up include files from the source directory itself rather than the
previously installed include files. To be sure I need a little more
information:
Did you build the entire tree -- in particular, did you build libstdc++
and libio?
What are the contents of your $objdir/libio (just the ls output is
fine).
Jeff
next reply other threads:[~1997-08-27 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-27 3:29 scott snyder [this message]
1997-08-27 3:29 ` A texinfo patch H.J. Lu
1997-08-27 5:21 ` Here are the g++ test results Jeffrey A Law
1997-08-27 5:35 ` libF77 N8TM
1997-08-27 5:35 ` egcs web page Jeffrey A Law
1997-08-27 5:59 ` g77 configuring, docs (was Re: 970825 Snapshot Available) Jeffrey A Law
1997-09-10 12:02 ` A texinfo patch Jim Wilson
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=m0x3ZBA-0004ecC@ocean.lucon.org \
--to=law@hurl.cygnus.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).