scripts/build/companion_tools/400-libtool.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jul 17 22:46:47 2011 +0200 (2011-07-17)
changeset 2892 aa934ec4b4ee
parent 2309 2e0f0757289d
permissions -rw-r--r--
cc/gcc: add the backend/frontend infra for final gcc

Currently, we issue the bare-metal compiler from the pass_1 & pass_2
core compilers, because the final gcc breaks while doing so.

This implies we have to build some libces during the start_files step,
instead of the standard libc step. This is the case for newlib.

By adding a backend/frontend infra to the final gcc, we can abstract
what backend to call: the standard backend for non-bare-metal gcc,
and the core backend for bare-metal.

This patch is just an no-op, it just adds the final backend and
frontend without changing the way bare-metal is built, to come in a
subsequent patch.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Build script for libtool
     2 
     3 CT_LIBTOOL_VERSION=2.2.6b
     4 
     5 do_companion_tools_libtool_get() {
     6     CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \
     7                {ftp,http}://ftp.gnu.org/gnu/libtool
     8 }
     9 
    10 do_companion_tools_libtool_extract() {
    11     CT_Extract "libtool-${CT_LIBTOOL_VERSION}"
    12     CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}"
    13     CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"
    14 }
    15 
    16 do_companion_tools_libtool_build() {
    17     CT_DoStep EXTRA "Installing libtool"
    18     mkdir -p "${CT_BUILD_DIR}/build-libtool"
    19     CT_Pushd "${CT_BUILD_DIR}/build-libtool"
    20     
    21     CT_DoExecLog CFG \
    22     "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}/configure" \
    23         --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
    24     CT_DoExecLog ALL make
    25     CT_DoExecLog ALL make install
    26     CT_Popd
    27     CT_EndStep
    28 }