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 (C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Shut off a stupid warning: preffered-stack-boundary must be between 4 ad 12,
7 diff -dur glibc-2.5.orig/sysdeps/i386/Makefile glibc-2.5/sysdeps/i386/Makefile
8 --- glibc-2.5.orig/sysdeps/i386/Makefile 2005-03-06 01:18:16.000000000 +0100
9 +++ glibc-2.5/sysdeps/i386/Makefile 2007-05-27 17:49:37.000000000 +0200
12 sysdep-CFLAGS += -mpreferred-stack-boundary=4
14 -sysdep-CFLAGS += -mpreferred-stack-boundary=2
15 +sysdep-CFLAGS += -mpreferred-stack-boundary=4
16 # Likewise, any function which calls user callbacks
17 uses-callbacks += -mpreferred-stack-boundary=4
18 # Likewise, any stack alignment tests