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 --- strace-orig/file.c 2008/05/20 04:56:18 1.92
2 +++ strace/file.c 2008/08/01 01:13:10 1.93
4 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
5 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
7 - * $Id: file.c,v 1.92 2008/05/20 04:56:18 roland Exp $
8 + * $Id: file.c,v 1.93 2008/08/01 01:13:10 roland Exp $
16 -#define dirent kernel_dirent
17 -#define dirent64 kernel_dirent64
18 -#include <linux/types.h>
19 -#include <linux/dirent.h>
22 +struct kernel_dirent {
23 + unsigned long d_ino;
24 + unsigned long d_off;
25 + unsigned short d_reclen;
29 -#define kernel_dirent dirent
30 +# define kernel_dirent dirent