gcc 3.4.0 testsuite gives over 5000 g++ errors

[Paul C. Leopardi]

Hi again, Answers below. Best regards
On Tuesday 04 May 2004 15:43, llewelly@xmission.com wrote:
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > It turns out that I had colorgcc installed and the SuSE rpm had put links
> > in /usr/local/bin from eg g++ to colorgcc.
>
> I haven't had colorgcc installed on any machine I own for over 3
>     years, so I had totally forgotten about it. But this seems to be
>     only part of the problem; it shouldn't have been using
>     /usr/local/bin/g++ in the first place.
Yes.

> > I uninstalled colorgcc, renamed gcc-3.4.0.obj and ran configure and "make
> > bootstrap" in a fresh directory, then ran "make -k check" again.
> >
> >                 === g++ Summary ===
> >
> > # of expected passes            8455
> > # of unexpected failures        1403
> > # of unexpected successes       7
> > # of expected failures          61
> > # of unresolved testcases       15
> > # of untested testcases         30
> > # of unsupported tests          68
> > /usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)
>
> This is completely mindboggling. Unless you have colorgcc installed in
>     /usr/bin too?
No.

> > I think the build must have failed in some cryptic way.
> > The output from "make bootstrap" is 12.9MB in size!
>
> Maybe I'm jumping at shadows, but that sounds a little large ... I
>     have  7028873 bytes (< 7MB) for the output of make boostrap-lean
>     of 3.4.0 (c, objc, c++, java, f77) on i686-freeBSD5.2 .
>
> > How do I check it to see
> > whether it succeeded? I thought that if it went all the way to the end it
> > must have succeeded?
>
> I still think it is more likely that something went wrong with
>     make check than with make bootstrap. Remember, almost all of the
>     libstdc++ tests succeed, and those use the 3.4.0 you just
>     built. So I *think* the newly built g++ binary is ok. It just isn't
>     getting run by 'make check'.
>
> > No?
> > Where does g++ get built to?
>
> It should be in objdir/gcc .
>
> > What file am I looking for?
The file g++ is in gcc-3.4.0-obj/gcc

> > How does runtest know where to find g++?
>
> I don't know. I seem to lack dejagnu info files for some reason. Could
>     you try aliasing 'runtest' to 'runtest -v' ?
I have done so and run "make -k check" again. I've attached the diff. In 
summary, nothing has chaned and runtest -v gives no extra info.

Should I ask on the dejagnu list?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: make-k-check.1.2.diff
Type: text/x-diff
Size: 13555 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc-help/attachments/20040504/6b3c54a6/attachment-0001.bin>