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 Enable building a pure soft-float compiler without the need for a software
2 floating point library.
4 diff -dur gcc-4.0.4.orig/gcc/config.gcc gcc-4.0.4/gcc/config.gcc
5 --- gcc-4.0.4.orig/gcc/config.gcc 2007-02-02 19:12:28.000000000 +0100
6 +++ gcc-4.0.4/gcc/config.gcc 2007-02-02 19:12:07.000000000 +0100
8 tm_defines="TARGET_BIG_ENDIAN_DEFAULT=1 $tm_defines"
11 - tmake_file="${tmake_file} arm/t-arm arm/t-linux"
12 + tmake_file="${tmake_file} arm/t-arm arm/t-linux arm/t-arm-elf"
13 extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"