scripts/build/companion_tools/100-m4.sh
author Bart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
changeset 2031 3917f2dafed1
parent 1728 60b7ebc4709a
child 2154 250cdcc86441
permissions -rw-r--r--
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
     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 ALL \
    21     "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \
    22         --prefix="${CT_TOOLS_OVERIDE_DIR}"
    23     CT_DoExecLog ALL make
    24     CT_DoExecLog ALL make install
    25     CT_Popd
    26     CT_EndStep
    27 }