scripts/build/companion_tools/100-m4.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 2154 250cdcc86441
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

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
}