glibc: Refactor startfiles/headers into do_libc_backend()

Refactor the contents of 'do_libc_start_files()' and 'do_libc()' into a
parameterized 'do_libc_backend()'. 'do_libc_start_files()' and 'do_libc()'
call 'do_libc_backend()' with either 'libc_mode=startfiles' or
'libc_mode=final' (respectively) so that the startfiles/headers and
the final libc builds are configured and built with the same options.

One example of where this is needed is when building a mips toolchain.
Previously, if you were building an n32 toolchain, you wouldn't have
noticed an issue, because if '-mabi' is not in CFLAGS, n32 is the
default:

http://sourceware.org/git/?p=glibc-ports.git;a=blob;f=sysdeps/mips/preconfigure;hb=HEAD

But when trying to build an o32 or n64 toolchain the build would
have failed. This is because (e)glibc expects "-mabi={o32,n32,n64}" to be
in CFLAGS, but was not previously provided in 'do_libc_start_files()'.
The build failure would happen in the shared-core gcc when it tries to
configure an n64 or o32 gcc with an n32 libc.

A simpler solution would have been to just add TARGET_CFLAGS to configure
in 'do_libc_start_files()', but this way makes configure and make
consistent for both steps.

Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>

 This is the README for crosstool-NG

 Crosstool-NG follows the autoconf dance. So, to get you

 kick-started, just run:

   ./configure --help

 You will find the documentation in the directory 'docs'.

 Here is a quick overview of what you'll find there:

   0 - Table of content

   1 - Introduction

   2 - Installing crosstool-NG

   3 - Configuring a toolchain

   4 - Building the toolchain

   5 - Using the toolchain

   6 - Toolchain types

   7 - Contributing

   8 - Internals

   A - Credits

   B - Known issues

   C - Misc. tutorials

 You can also point your browser at:

   http://ymorin.is-a-geek.org/projects/crosstool

 Aloha!