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 Correctly check for g++ existence.
3 Copyright 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 Licensed to you as dmalloc-5.5.2 is.
6 diff -dur dmalloc-5.5.2.orig/configure dmalloc-5.5.2/configure
7 --- dmalloc-5.5.2.orig/configure 2007-05-18 11:40:31.000000000 +0200
8 +++ dmalloc-5.5.2/configure 2007-05-18 11:42:02.000000000 +0200
12 # see if we actually have a CXX program
13 -if test "$ac_cv_prog_CXX" = "" -o ! -x "$ac_cv_prog_CXX"; then
14 +if test "$ac_cv_prog_CXX" = "" -o ! -x `which "$ac_cv_prog_CXX"`; then
15 { echo "$as_me:$LINENO: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&5
16 echo "$as_me: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&2;}