That is to say:
#make menuconfig
Loadable module support --->
[*] Enable loadable module support x x
[ ] Set version information on all module symbols x x
[ ] Kernel module loader
Clear the [*] before "Set version information on all module symbols"
Rebuild your kernel and module then will be ok.
But that is not good idea for stability.
canny
----- Original Message -----
From: "Keith Owens" <kaos@ocs.com.au>
To: "Gary Cote" <gcote@transat-tech.com>
Cc: <linux-net@vger.kernel.org>
Sent: Monday, March 24, 2003 1:35 PM
Subject: Re: unresolved symbol: sockfd_lookup
> On Sun, 23 Mar 2003 22:35:46 -0600,
> Gary Cote <gcote@transat-tech.com> wrote:
> >I'm trying to move my linux module from the development
> >environment to the distribution environment, but I'm getting
> >an unresolved symbol error (sockfd_lookup) when I insmod it.
> >2.4.18-3 is RH 7.3 out of the box...driver is compiled against same
>
> Not quite, the kernel is compiled with modversions but your modules has
> no modversions.
>
> ># insmod wtp.o
> >wtp.o: unresolved symbol sockfd_lookup
>
> No modversion in module. The combination of a versioned kernel and a
> non-versioned module should work. Send me the output from
>
> grep sockfd_lookup /proc/ksyms
> insmod -v wtp.o
>
> -
> : send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
