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>

# Wrapper to build the companion tools facilities

# List all companion tools facilities, and parse their scripts

CT_COMP_TOOLS_FACILITY_LIST=

for f in "${CT_LIB_DIR}/scripts/build/companion_tools/"*.sh; do

    _f="$(basename "${f}" .sh)"

    _f="${_f#???-}"

    __f="CT_COMP_TOOLS_${_f}"

    if [ "${!__f}" = "y" ]; then

        CT_DoLog DEBUG "Enabling companion tools '${_f}'"

        . "${f}"

        CT_COMP_TOOLS_FACILITY_LIST="${CT_COMP_TOOLS_FACILITY_LIST} ${_f}"

    else

        CT_DoLog DEBUG "Disabling companion tools '${_f}'"

    fi

done

# Download the companion tools facilities

do_companion_tools_get() {

    for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do

        do_companion_tools_${f}_get

    done

}

# Extract and patch the companion tools facilities

do_companion_tools_extract() {

    for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do

        do_companion_tools_${f}_extract

    done

}

# Build the companion tools facilities

do_companion_tools() {

    for f in ${CT_COMP_TOOLS_FACILITY_LIST}; do

        do_companion_tools_${f}_build

    done

}