Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
Answers and many questions below.
Best regards

On Tuesday 04 May 2004 02:08, llewelly@xxxxxxxxxxxx wrote:
> "Paul C. Leopardi" <leopardi@xxxxxxxxxxxxxx> writes:
> > Hi,
> > I checked versions as you suggested.
> > runtest -V
> > Expect version is       5.38.0
> > Tcl version is          8.4
> > Framework version is    1.4.3
> >
> > I also rebuilt gcc 3.4.0 and re-ran the tests.
> > http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00137.html
> >
> > I don't understand why the heading is "Results for 3.3.2 20031216
> > (prerelease)
>
> This is really strange. I guess the dejagnu is running you old g++
>     3.3.2 instead of the g++ you just built. I can't imagine *why*,
>     however. Maybe an alias is interfering?

I tried the test suite again, after renaming /usr/local/bin 
to /usr/local/bin.old, and the test used /usr/bin/g++ this time.

		=== g++ Summary ===

# of expected passes		8454
# of unexpected failures	1404
# 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)

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 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)

I think the build must have failed in some cryptic way. 
The output from "make bootstrap" is 12.9MB in size! 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? No?
Where does g++ get built to? What file am I looking for?
How does runtest know where to find g++?
Sorry for all the questions. I am such a noob. Maybe this is all documented 
somewhere?
Should I direct these questions to the main gcc mailing list, or one of the 
suse mailing lists?

> > (SuSE Linux) testsuite on x86_64-suse-linux-gnu". I thought I was testing
> > 3.4.0? The test results themselves say, "LAST_UPDATED: Obtained from CVS:
> > -rgcc_3_4_0_release".
> >
> > Anyway, the result is about the same. Over 5000 g++ errors.
> >
> > I must have something configured wrong. What could it be?
>
> [snip]

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux