cc/gcc: do not use the core pass-2 to build the baremetal compiler

In case we build a baremetal compiler, use the standard passes:
- core_cc is used to build the C library;
- as such, it is meant to run on build, not host;
- the final compiler is meant to run on host;

As the current final compiler step can not build a baremetal compiler,
call the core backend from the final step.

NB: Currently, newlib is built during the start_files pass, so we have
to have a core compiler by then... Once we can build the baremetal
compiler from the final cc step, then we can move the newlib build to
the proper step, and then get rid of the core pass-1 static compiler...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# Build script for m4

CT_M4_VERSION=1.4.13

do_companion_tools_m4_get() {

    CT_GetFile "m4-${CT_M4_VERSION}" \

               {ftp,http}://ftp.gnu.org/gnu/m4

}

do_companion_tools_m4_extract() {

    CT_Extract "m4-${CT_M4_VERSION}"

    CT_Patch "m4" "${CT_M4_VERSION}"

}

do_companion_tools_m4_build() {

    CT_DoStep EXTRA "Installing m4"

    mkdir -p "${CT_BUILD_DIR}/build-m4"

    CT_Pushd "${CT_BUILD_DIR}/build-m4"

    CT_DoExecLog CFG \

    "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \

        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

    CT_DoExecLog ALL make

    CT_DoExecLog ALL make install

    CT_Popd

    CT_EndStep

}