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 --- gcc-4.2.1-stock/gcc/config/alpha/linux-unwind.h 2005-06-24 20:22:41.000000000 -0500
2 +++ gcc-4.2.1/gcc/config/alpha/linux-unwind.h 2007-09-01 20:21:34.000000000 -0500
3 @@ -29,6 +29,9 @@ Boston, MA 02110-1301, USA. */
4 /* Do code reading to identify a signal frame, and set the frame
5 state data appropriately. See unwind-dw2.c for the structs. */
7 +/* Don't use this if inhibit_libc is set
8 + The build for this target will fail trying to include missing headers */
11 #include <sys/ucontext.h>
13 @@ -80,3 +83,4 @@ alpha_fallback_frame_state (struct _Unwi
14 fs->retaddr_column = 64;
15 return _URC_NO_REASON;
17 +#endif /* inhibit_libc */