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 --- glibc-2.5/sysdeps/unix/sysv/linux/alpha/sigsuspend.S.orig 2006-10-22 22:17:01.000000000 +0200
2 +++ glibc-2.5/sysdeps/unix/sysv/linux/alpha/sigsuspend.S 2006-10-22 22:18:05.000000000 +0200
4 libc_hidden_def (__sigsuspend)
5 weak_alias (__sigsuspend, sigsuspend)
6 strong_alias (__sigsuspend, __libc_sigsuspend)
8 +#ifndef NO_CANCELLATION
9 + .globl __sigsuspend_nocancel;
11 + .type __sigsuspend_nocancel, @function;
12 + .usepv __sigsuspend_nocancel, std;
14 +__LABEL(__sigsuspend_nocancel)
18 + lda v0, SYS_ify(sigsuspend);
19 + call_pal PAL_callsys;
20 + bne a3, SYSCALL_ERROR_LABEL;
23 + .size __sigsuspend_nocancel, .-__sigsuspend_nocancel