RFE: long overdue method to indicate bootstrap success

Dennis Clarke dclarke@blastwave.org
Thu Mar 21 20:16:00 GMT 2013


> > I see "Error 2" as the last line of output.
> 
> It's not, it means something failed. Have you tried redirecting the
> output (both stdout and stderr) to a file and seeing what failed?

I was hoping you wouldn't say that :-\

Well I do have the entire build process captured to a file. So that may help.
I am guessing that there was something amiss with either ada ( gnat ) or go.
Simply because the results I did get, were fairly horrific for gnat and go : 

    http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02203.html


where I see :

                === gnat Summary ===

# of expected passes            8
# of unexpected failures        792
# of expected failures          17
# of unresolved testcases       344
# of unsupported tests          13
/usr/local/gcc4/bin/gnatmake version 4.7.2

                === go Summary ===

# of expected passes            1087
# of unexpected failures        651
# of untested testcases         555
# of unresolved testcases       7
/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/gcc/testsuite/go/../../gccgo  version 4.8.0 20130316 (prerelease) (Blastwave.org Inc. Thu Mar 21 05:18:45 GMT 2013) 


eek :-P

> If bootstrap completes successfully you don't get that error.

For the sake of experimentation I will drop both ada and go from the list of 
languages to build for, just to see what I get.  However I guess I have to
grep through the output from the build to see w5 : what, where, why it went wrong. 

dc



More information about the Gcc-help mailing list