Satish Eerpini wrote:
> hi everyone , i was trying to patch kdb with CentOS 5.0 kernel
> (2.6.18-8) , and had a few rejects ( which i am still trying to
> resolve) ,.... but apart from the rejects during the kernel
> compilation i got the following error which does not seem to have
> anything to do with the rejects ............
> i have got an error in a kdb module, which has nothing to do with the
> rejected patches ( or so i guess ) :

Hi Satish,

I set up a new build area with upstreams 2.6.18-8 (not CentOS) with
kdb-v4.4-2.6.18-common-1 and kdb-v4.4-2.6.18-i386-1. The patches were
applied fine (with a few offset lines in two files). I used the
linux/arch/i386/defconfig of the kernel source as base, turned on
CONFIG_DEBUG_KERNEL, and took all default values in 'make oldconfig'.
The kernel was built fine with CONFIG_KDB_MODULES set to either 'y'
or 'm'.

My guess is that your problem was CentOS specific?

Regards,
 - jay


> 
>             kdb/modules/kdbm_pg.c: In function 'kdbm_show_page':
>             kdb/modules/kdbm_pg.c:349: error: implicit declaration
> of function 'PageChecked'
>             kdb/modules/kdbm_pg.c: In function 'kdbm_inode':
>             kdb/modules/kdbm_pg.c:507: error: 'struct inode' has no
> member named 'u'
> 
>  the code(in kdb/modules/kdbm_pg.c) which is causing the second error
> is something like this :
> 
>            iaddr += offsetof(struct inode, u);
> 
> what i am not able to understand is that if 'u' is not a correct
> member of the inode , .. then what did they( whoever wrote this piece
> code) intend by 'u' ? , .....
> 
> ....
> and for the first error , ... i just checked out the code ....
> according to the line no shown in the error .....the code is :
> 
>            kdb_page_flags(page, Checked);
> 
> and i don't see any function PageChecked ....! so what can the error
> actually mean ??
> 
> Thanks in advance
> Satish
> 
> --
> http://satish.playdrupal.com
> 
> 
> 

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.

Reply via email to