* Deal with libgcc's move from gnu/usr.bin/cc to gnu/lib.   Move was necessary as libgcc should be built with the freshly built   compiler and thus we must wait until the freshly built bits have been   installed somewhere so we can use them.  libgcc presence in gnu/usr.bin/cc/   gets in the way of building the new compiler.  We could have either   cd'ed to specific directories w/in gnu/usr.bin/cc/ and built and installed   individual bits, or move libgcc out of the way and let our normal subdir   building process work.
* Deal with libgcc's move from gnu/usr.bin/cc to gnu/lib.
  Move was necessary as libgcc should be built with the freshly built
  compiler and thus we must wait until the freshly built bits have been
  installed somewhere so we can use them.  libgcc presence in gnu/usr.bin/cc/
  gets in the way of building the new compiler.  We could have either
  cd'ed to specific directories w/in gnu/usr.bin/cc/ and built and installed
  individual bits, or move libgcc out of the way and let our normal subdir
  building process work.

* Don't build libgcc in "bootstrap-libraries:" target it should not be
  assumed the currently installed compiler can correctly build libgcc.
  (as is the case for g++ 2.7.2 and EGCS' libgcc)

jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase