Russell,
When can I get information on modifing 'extractinfo.pl' (extractinfo.perl)
to work with the latest and greatest tools (i.e. Binutils v2.9.1.0.19a).
Thanks,
Jason
----------
From: Russell King [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 28, 1999 12:25 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: ARM-Linux on Brutus...
Steve Kipisz said:
> I can't remember how I solved this problem. I remembered having
the
> problem, I just can't remember how I solved it! Here is my file:
>
> /*
> * *** THIS FILE IS AUTOMATICALLY GENERATED. DO NOT EDIT! ***
> */
> unsigned long tss_memmap = 696;
> #define __HAS_tss_memmap
> unsigned long mm = 708;
> #define __HAS_mm
> unsigned long pgd = 4;
> #define __HAS_pgd
> unsigned long tss_save = 692;
> #define __HAS_tss_save
> unsigned long tss_fpesave = 552;
> #define __HAS_tss_fpesave
It is not a good idea to send people this file! There is a good
reason why it's automatically generated (and it's not to make the
build process harder). The constants are highly kernel-version
dependent.
The problem is most likely going to be an incompatability between
the 'extractinfo.pl' perl script and your version of objdump. When
using 2.0 kernel source, you either /must/ use the binutils-2.7
a.out
tools, /or/ fix 'extractinfo.pl' so that it can parse your binutils'
objdump output.
--
Russell King ([EMAIL PROTECTED])
unsubscribe: body of `unsubscribe linux-arm' to
[EMAIL PROTECTED]
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
