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>
2 CT_LOCAL_TARBALLS_DIR="${HOME}/src"
7 CT_TARGET_CFLAGS="-mfloat-gprs=double -Wa,-me500x2"
9 CT_ARCH_powerpc_ABI_SPE=y
10 CT_TARGET_VENDOR="e500v2"
12 CT_KERNEL_V_2_6_36_4=y
13 CT_BINUTILS_V_2_20_1a=y
14 CT_BINUTILS_EXTRA_CONFIG_ARRAY="--enable-spe=yes --enable-e500x2 --with-e500x2"
15 CT_BINUTILS_FOR_TARGET=y
16 CT_CC_GCC_SHOW_LINARO=y
19 CT_CC_EXTRA_CONFIG_ARRAY="--with-long-double-128"
20 # CT_CC_GCC_ENABLE_TARGET_OPTSPACE is not set
21 # CT_CC_GCC_SJLJ_EXCEPTIONS is not set
22 CT_LIBC_EGLIBC_V_2_10=y
23 # CT_LIBC_GLIBC_FORCE_UNWIND is not set
24 CT_LIBC_GLIBC_USE_PORTS=y
28 CT_GDB_NATIVE_STATIC=y