scripts/build/companion_tools/100-m4.sh
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Tue Oct 16 20:57:44 2012 +0200 (2012-10-16)
changeset 3079 37831a33e07e
parent 2154 250cdcc86441
permissions -rw-r--r--
kernel/linux: fix using custom location

Currently, extract and patch are skipped as thus:
- using a custom directory of pre-installed headers
- a correctly named directory already exists

Otherwise, extract and patch are done.

The current second condition is wrong, because it allows the following
sequence to happen:
- a non-custom kernel is used
- a previous build only partially extracted the non-custom sources
- that p[revious build broke during extraction (eg. incomplete tarball...)
- a subsequent build will find a properly named directory, and will
thus skip extract and patch, which is wrong

Fix that by following the conditions in this table:

Type | Extract | Patch
----------------------+---------+-------
Pre-installed headers | N | N
custom directory | N | N
custom tarball | Y | N
mainstream tarball | Y | Y

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: David Holsgrove <david.holsgrove@xilinx.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 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 }