scripts/build/companion_tools/100-m4.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jan 01 17:49:44 2012 +0100 (2012-01-01)
changeset 2924 0eab838768b1
parent 2154 250cdcc86441
permissions -rw-r--r--
cc/gcc: install the core compilers in the build-tools dir

There really is no good reason to install the core compilers in their
own places, one for each pass. We can install them with the other
build tools.

Also, this implies that:
- there are fewer directories to save/restore
- there are fewer symlinks to create for binutils
- the PATH is shorter

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