[Top] [All Lists]

Re: Unresolved Symbols problem w/ 2.4.1-XFS cvs

To: "Chris 'Chipper' Chiapusio" <chipper@xxxxxxxxxx>
Subject: Re: Unresolved Symbols problem w/ 2.4.1-XFS cvs
From: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Wed, 14 Feb 2001 15:13:58 +1100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Your message of "Tue, 13 Feb 2001 22:06:59 CDT." <Pine.LNX.4.30.0102132204170.25289-200000@chipsworld.llamas.net>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Tue, 13 Feb 2001 22:06:59 -0500 (EST), 
"Chris 'Chipper' Chiapusio" <chipper@xxxxxxxxxx> wrote:
>a current cvs checkout (as of 02/12/01) gives me mostly usable modules,
>only two are not working:
>[root@zhadum /root]# depmod -ae
>depmod: *** Unresolved symbols in
>depmod:        name_to_kdev_t

Known bug in the md driver, fixed in later kernels.  IOW, not our problem :).

>depmod: *** Unresolved symbols in
>depmod:        rtnetlink_links
>depmod:        __rta_fill
>depmod:        rtnetlink_put_metrics
>depmod:        rtnl

This one is strange.  I cannot reproduce the problem on 2.4.2-pre3 with
your .config but I cannot see any changes between 2.4.1 and 2.4.2-pre3
that would affect rtnetlink.  I need the output from

strings -a /lib/modules/2.4.1-XFStest2/kernel/net/ipv6/ipv6.o | grep rtn
strings -a net/netsyms.o | grep rtn

The latter command needs to be issued in the top level linux directory.

<Prev in Thread] Current Thread [Next in Thread>