2002-04-12 11:59:49

by Dumas Patrice

[permalink] [raw]
Subject: error when insmod nfsd: unresolved symbol nfsd_linkage

Hi,
I have just compiled linux-2.4.18 with linux-2.4.18-NFS_ALL.dif applied. All
the nfs stuff was compiled as modules (without over TCP support). I made
some changes in lockd/svcproc.c, but I touched nothing anywhere else. I am on a
redhat 7.2, but the kernel is a normal kernel.

Now, when I try to insmod the nfsd module (after sunrpc and lockd), I get

./nfsd.o: unresolved symbol nfsd_linkage

gcc -v gives
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)


Pat

_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs


2002-04-12 12:34:47

by Trond Myklebust

[permalink] [raw]
Subject: Re: error when insmod nfsd: unresolved symbol nfsd_linkage

>>>>> " " == Dumas Patrice <[email protected]> writes:

> Hi, I have just compiled linux-2.4.18 with
> linux-2.4.18-NFS_ALL.dif applied. All the nfs stuff was
> compiled as modules (without over TCP support). I made some
> changes in lockd/svcproc.c, but I touched nothing anywhere
> else. I am on a redhat 7.2, but the kernel is a normal kernel.

> Now, when I try to insmod the nfsd module (after sunrpc and
> lockd), I get

> ./nfsd.o: unresolved symbol nfsd_linkage

The above usually means that the kernel was compiled without
'CONFIG_NFSD=m' being set.
You probably forgot to run 'make oldconfig' after changing the .config
file by hand or something like that.

Cheers,
Trond

_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs