RFE: long overdue method to indicate bootstrap success
Jonathan Wakely
jwakely.gcc@gmail.com
Thu Mar 21 18:08:00 GMT 2013
On 21 March 2013 15:25, Dennis Clarke wrote:
>
> One of the items that I personally feel would be of great value would be some
> mechanism to indicate that the bootstrap process actually succeeds. At the
> moment my 4.8.0 RC bootstrap simply comes to a grinding halt with an
> error message :
> .
> .
> .
> ranlib rts_sparcv8plus/libgnarl.a
> /usr/ccs/bin/ar rc rts_sparcv8plus/libgmem.a \
> rts_sparcv8plus/memtrack.o
> ranlib rts_sparcv8plus/libgmem.a
> chmod a-wx rts_sparcv8plus/*.ali
> touch ../stamp-gnatlib-rts_sparcv8plus
> gmake[7]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/gcc/ada'
> mv -f libgna*.so rts_sparcv8plus
> gmake[6]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/gcc/ada'
> gmake[5]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/gcc/ada'
> rm -rf adainclude
> rm -rf adalib
> ln -s ../../.././gcc/ada/rts_sparcv8plus adainclude
> ln -s ../../.././gcc/ada/rts_sparcv8plus adalib
> true DO=all multi-do # /usr/local/bin/gmake
> gmake[4]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/sparc64-sun-solaris2.10/sparcv8plus/libada'
> gmake[3]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/sparc64-sun-solaris2.10/libada'
> gmake[2]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001/sparc64-sun-solaris2.10/libada'
> gmake[1]: Leaving directory `/usr/local/build/gcc-4.8.0-RC-20130316_sparc64-sun-solaris2.10.001'
> gmake: *** [all] Error 2
>
> bash-4.2$
>
>
> Well what does that mean ? I sure can't think "success" is the word of the day when 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?
If bootstrap completes successfully you don't get that error.
More information about the Gcc-help
mailing list