RFE: long overdue method to indicate bootstrap success

[Dennis Clarke <dclarke at blastwave dot org>]

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.

Let's check the few things that do exist as signposts : 

bash-4.2$ cat  stage_final
stage3
bash-4.2$ cat stage_current
stage3
bash-4.2$ cat stage_last
stage3

Great. 

So if there is any way at all to insert an RFE into the GCC bootstrap process I would
love to see more signposts , intermediate files, just a simple "touch stage_current_XXX"
where the XXX are digits that indicate how far into the bootstrap process things
have proceeded.  

At the very least, when the entire bootstrap does finish, perhaps a simple message
to the effect of "bootstrap complete".  Nothing fancy. 

Really, I can not tell if this did succeed or not unless I run the testsuite, which, I would
not bother with if I see the word "Error" as the last line of output. However, I just
can't tell and really there is no way to know.

Dennis