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 reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"
2 reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"
3 reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g., MPC8548,
4 MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.6.0,
5 for e500v2 DPFP support) and will generate appropriate dual-precision
6 floating point instructions by default.
8 Note: If building a Linux kernel with this toolchain, you will want to make
9 sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE ABI/instructions
10 from getting into the kernel (which is currently unsupported). At this time,
11 the kernel build system properly passes those two options, but older kernels
12 were only passing -mno-spe by default."