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 Original patch from gentoo: gentoo/src/patchsets/gcc/4.3.1/gentoo/66_all_gcc43-pr25343.patch
2 http://gcc.gnu.org/PR25343
6 2008-04-27 Roman Zippel <zippel@linux-m68k.org>
8 * config/host-linux.c (TRY_EMPTY_VM_SPACE): Define for __mc68000__.
10 diff -durN gcc-4.3.1.orig/gcc/config/host-linux.c gcc-4.3.1/gcc/config/host-linux.c
11 --- gcc-4.3.1.orig/gcc/config/host-linux.c 2007-08-02 12:49:31.000000000 +0200
12 +++ gcc-4.3.1/gcc/config/host-linux.c 2008-06-10 14:58:28.000000000 +0200
14 # define TRY_EMPTY_VM_SPACE 0x8000000000
15 #elif defined(__sparc__)
16 # define TRY_EMPTY_VM_SPACE 0x60000000
17 +#elif defined(__mc68000__)
18 +# define TRY_EMPTY_VM_SPACE 0x40000000
20 # define TRY_EMPTY_VM_SPACE 0