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 # powerpc specific configuration file
3 config ARCH_powerpc_ABI
5 default "" if ARCH_powerpc_ABI_DEFAULT
6 default "eabi" if ARCH_powerpc_ABI_EABI
7 default "spe" if ARCH_powerpc_ABI_SPE
12 default ARCH_powerpc_ABI_DEFAULT
14 config ARCH_powerpc_ABI_DEFAULT
18 The default ABI (System V.4).
20 config ARCH_powerpc_ABI_EABI
25 The Embedded ABI (stack alignment of 8 bytes, etc).
27 config ARCH_powerpc_ABI_SPE
31 Add support for the Signal Processing Engine. This will set up
32 the toolchain so that it supports the SPE ABI extensions. This
33 mainly targets Freescale e500 processors.
35 Setting this option will append "spe" to the end of your target
36 tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
37 configure/build system will know to include SPE ABI support. It
38 will also automatically add "-mabi=spe -mspe" to your TARGET_CFLAGS,
39 and "--enable-e500_double" to your CC_EXTRA_CONFIG_ARRAY, so you
40 do not need to explicitly add them.