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 diff -u binutils-2.20.orig/configure binutils-2.20/configure
3 diff -durN binutils-2.20.1.orig/configure binutils-2.20.1/configure
4 --- binutils-2.20.1.orig/configure 2010-08-17 19:32:07.000000000 +0200
5 +++ binutils-2.20.1/configure 2010-08-17 19:32:22.000000000 +0200
7 noconfigdirs="$noconfigdirs target-libffi target-qthreads"
10 - arm*-*-linux-gnueabi)
11 + arm*-*-linux-*gnueabi)
12 noconfigdirs="$noconfigdirs target-qthreads"
13 case ${with_newlib} in
14 no) noconfigdirs="$noconfigdirs target-newlib target-libgloss"
15 diff -durN binutils-2.20.1.orig/configure.ac binutils-2.20.1/configure.ac
16 --- binutils-2.20.1.orig/configure.ac 2010-08-17 19:32:07.000000000 +0200
17 +++ binutils-2.20.1/configure.ac 2010-08-17 19:32:22.000000000 +0200
19 noconfigdirs="$noconfigdirs target-libffi target-qthreads"
22 - arm*-*-linux-gnueabi)
23 + arm*-*-linux-*gnueabi)
24 noconfigdirs="$noconfigdirs target-qthreads"
25 case ${with_newlib} in
26 no) noconfigdirs="$noconfigdirs target-newlib target-libgloss"