Amitava Dutta wrote:
Here's from the output of "make -k check" without the "-j" option.
Notice that there's no # for the libstdc++.
=== gcc Summary ===
# of expected passes 18369
# of unexpected failures 22530
# of expected failures 226
# of unresolved testcases 7716
# of unsupported tests 1016
=== g++ Summary ===
# of expected passes 9839
# of unexpected failures 8301
# of unexpected successes 1
# of expected failures 143
# of unresolved testcases 122
# of unsupported tests 291
=== gfortran Summary ===
# of expected passes 15952
# of unexpected failures 9498
# of expected failures 9
# of unsupported tests 1503
=== libstdc++ Summary ===
=== libgomp Summary ===
# of expected passes 1057
# of unexpected failures 1061
# of unsupported tests 137
What am I doing wrong?
You cannot tell from the test summary. You should look at the various
testsuite *.log files and analyze the failures on a case by case basis.
Usually forthe number of failures you are seeing, there is a common
problem that is causing them all.
You can look at: http://gcc.gnu.org/ml/gcc-testresults/ to see how your
results compare against those of others.
David Daney
Best regards
Amitava Dutta
--- On Thu, 5/14/09, Amitava Dutta <ad_101@xxxxxxxxx> wrote:
From: Amitava Dutta <ad_101@xxxxxxxxx>
Subject: Re: built gcc-4.4.0, most tests failed, is it usable?
To: "GCC Help" <gcc-help@xxxxxxxxxxx>
Date: Thursday, May 14, 2009, 12:35 PM
Thanks.
Started the "make -k check" again without -j option,
will post summary tomorrow.
Best regards
Amitava Dutta
--- On Thu, 5/14/09, Ian Lance Taylor <iant@xxxxxxxxxx>
wrote:
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Subject: Re: built gcc-4.4.0, most tests failed, is it
usable?
To: ad_101@xxxxxxxxx
Cc: "GCC Help" <gcc-help@xxxxxxxxxxx>
Date: Thursday, May 14, 2009, 11:49 AM
Amitava Dutta <ad_101@xxxxxxxxx>
writes:
I built GCC 4.4.0 on a Sparc Solaris 10.
The build went thru fine, but most of the tests
failed,
last fragment from make check is below.
When you run "make check", don't use the -j option.
It is doing
something which is not supported by your host
tools.
make -jN check is
only well-tested on GNU/Linux. If you have the
time,
it would be
helpful if you could look into the problems on your
system
and fix them.
Ian
