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 # MicroBlaze specific config options
3 ## depends on EXPERIMENTAL
5 ## select ARCH_SUPPORT_ARCH
6 ## select ARCH_FLOAT_SW
7 ## select ARCH_SUPPORTS_BOTH_ENDIAN
8 ## select ARCH_DEFAULT_BE
9 ## select ARCH_SUPPORTS_BOTH_MMU
10 ## select ARCH_DEFAULT_HAS_MMU
12 ## help The MicroBlaze architecture, as defined by:
13 ## help http://www.xilinx.com/
15 ## help Upstream projects do not currently provide
16 ## help full support for the microblaze architecture
17 ## help and as such, this is marked as EXPERIMENTAL
20 ## help Support is being added for a modern gcc,
21 ## help binutils and gdb along with nptl threading
22 ## help in eglibc for microblaze.