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 -durN gcc-4.4.0.orig/include/libiberty.h gcc-4.4.0/include/libiberty.h
2 --- gcc-4.4.0.orig/include/libiberty.h 2008-06-24 03:42:31.000000000 +0200
3 +++ gcc-4.4.0/include/libiberty.h 2009-05-27 21:38:24.000000000 +0200
5 /* Like sprintf but provides a pointer to malloc'd storage, which must
6 be freed by the caller. */
8 +/* asprintf may be declared as a macro by glibc with __USE_FORTIFY_LEVEL. */
10 extern int asprintf (char **, const char *, ...) ATTRIBUTE_PRINTF_2;
14 #if !HAVE_DECL_VASPRINTF
15 /* Like vsprintf but provides a pointer to malloc'd storage, which