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>
3 ## depends on ! WINDOWS && ! BARE_METAL && ARCH_USE_MMU
5 ## select LIBC_SUPPORT_NPTL
6 ## select CC_CORE_PASSES_NEEDED
8 ## help The de-facto standard for Linux distributions.
9 ## help Feature-rich, but large... Most usefull for desktop-like systems.
13 prompt "glibc version"
14 # Don't remove next line
15 # CT_INSERT_VERSION_BELOW
17 config LIBC_GLIBC_V_2_17
21 config LIBC_GLIBC_V_2_16_0
25 config LIBC_GLIBC_V_2_15
29 config LIBC_GLIBC_V_2_14_1
33 config LIBC_GLIBC_V_2_14
37 config LIBC_GLIBC_V_2_13
41 config LIBC_GLIBC_V_2_12_2
45 config LIBC_GLIBC_V_2_12_1
49 config LIBC_GLIBC_V_2_11_1
53 config LIBC_GLIBC_V_2_11
57 config LIBC_GLIBC_V_2_10_1
60 select LIBC_GLIBC_USE_PORTS
62 config LIBC_GLIBC_V_2_9
66 config LIBC_GLIBC_V_2_8
74 # Don't remove next line
75 # CT_INSERT_VERSION_STRING_BELOW
76 default "2.17" if LIBC_GLIBC_V_2_17
77 default "2.16.0" if LIBC_GLIBC_V_2_16_0
78 default "2.15" if LIBC_GLIBC_V_2_15
79 default "2.14.1" if LIBC_GLIBC_V_2_14_1
80 default "2.14" if LIBC_GLIBC_V_2_14
81 default "2.13" if LIBC_GLIBC_V_2_13
82 default "2.12.2" if LIBC_GLIBC_V_2_12_2
83 default "2.12.1" if LIBC_GLIBC_V_2_12_1
84 default "2.11.1" if LIBC_GLIBC_V_2_11_1
85 default "2.11" if LIBC_GLIBC_V_2_11
86 default "2.10.1" if LIBC_GLIBC_V_2_10_1
87 default "2.9" if LIBC_GLIBC_V_2_9
88 default "2.8" if LIBC_GLIBC_V_2_8