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.18-orig/configure binutils-2.18/configure
2 --- binutils-2.18-orig/configure 2007-08-06 16:29:40.000000000 -0400
3 +++ binutils-2.18/configure 2007-09-27 22:41:51.000000000 -0400
4 @@ -6125,10 +6125,10 @@
5 *" texinfo "*) MAKEINFO='$$r/$(BUILD_SUBDIR)/texinfo/makeinfo/makeinfo' ;;
8 - # For an installed makeinfo, we require it to be from texinfo 4.4 or
9 + # For an installed makeinfo, we require it to be from texinfo 4.6 or
10 # higher, else we use the "missing" dummy.
11 if ${MAKEINFO} --version \
12 - | egrep 'texinfo[^0-9]*([1-3][0-9]|4\.[4-9]|[5-9])' >/dev/null 2>&1; then
13 + | egrep 'texinfo[^0-9]*(4\.([6-9]|[1-9][0-9])|[5-9]|[1-9][0-9])' >/dev/null 2>&1; then
16 MAKEINFO="$MISSING makeinfo"