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>
richard@1728
     1
# Build script for m4
richard@1728
     2
richard@1728
     3
CT_M4_VERSION=1.4.13
richard@1728
     4
richard@1728
     5
do_companion_tools_m4_get() {
richard@1728
     6
    CT_GetFile "m4-${CT_M4_VERSION}" \
richard@1728
     7
               {ftp,http}://ftp.gnu.org/gnu/m4
richard@1728
     8
}
richard@1728
     9
richard@1728
    10
do_companion_tools_m4_extract() {
richard@1728
    11
    CT_Extract "m4-${CT_M4_VERSION}"
yann@1901
    12
    CT_Patch "m4" "${CT_M4_VERSION}"
richard@1728
    13
}
richard@1728
    14
richard@1728
    15
do_companion_tools_m4_build() {
richard@1728
    16
    CT_DoStep EXTRA "Installing m4"
richard@1728
    17
    mkdir -p "${CT_BUILD_DIR}/build-m4"
richard@1728
    18
    CT_Pushd "${CT_BUILD_DIR}/build-m4"
richard@1728
    19
    
anthony@2154
    20
    CT_DoExecLog CFG \
richard@1728
    21
    "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \
yann@2309
    22
        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
richard@1728
    23
    CT_DoExecLog ALL make
richard@1728
    24
    CT_DoExecLog ALL make install
richard@1728
    25
    CT_Popd
richard@1728
    26
    CT_EndStep
richard@1728
    27
}