Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
samples/powerpc-e300c3-linux-gnu/crosstool.config
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2953 b0f1b8711716
child 3175 efad82bf7b9b
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 
     1 CT_EXPERIMENTAL=y

     2 CT_LOCAL_TARBALLS_DIR="${HOME}/src"

     3 CT_SAVE_TARBALLS=y

     4 CT_ARCH_CPU="e300c3"

     5 CT_ARCH_TUNE="e300c3"

     6 CT_ARCH_powerpc=y

     7 CT_TARGET_VENDOR="e300c3"

     8 CT_KERNEL_linux=y

     9 CT_KERNEL_V_2_6_36_4=y

    10 CT_BINUTILS_V_2_21_1a=y

    11 CT_BINUTILS_FOR_TARGET=y

    12 CT_CC_V_4_5_2=y

    13 CT_CC_LANG_CXX=y

    14 CT_CC_EXTRA_CONFIG_ARRAY="--with-long-double-128"

    15 # CT_CC_GCC_ENABLE_TARGET_OPTSPACE is not set

    16 # CT_CC_GCC_SJLJ_EXCEPTIONS is not set

    17 CT_LIBC_EGLIBC_V_2_12=y

    18 # CT_LIBC_GLIBC_FORCE_UNWIND is not set

    19 CT_LIBC_GLIBC_USE_PORTS=y

    20 CT_GMP_V_5_0_1=y

    21 CT_MPFR_V_3_0_0=y

    22 CT_PPL_V_0_10_2=y

    23 CT_CLOOG_V_0_15_10=y

    24 CT_MPC_V_0_8_2=y
crosstool-ng