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.
# uname -a
Linux wain 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown
2.4.18-3 is RH 7.3 out of the box...driver is compiled against same
# insmod wtp.o
wtp.o: unresolved symbol sockfd_lookup
wtp.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.
I *am* the module supplier, damnit, and feeling very inadequate
thankyouverymuch.
# nm wtp.o | grep sockfd_lookup
U sockfd_lookup
Yep, it's unresolved alright.
# grep sockfd_lookup /boot/System.map
c01c28f0 T sockfd_lookup
c02455f7 ? __kstrtab_sockfd_lookup
c024b728 ? __ksymtab_sockfd_lookup
# ls -l /boot/System.map
lrwxrwxrwx (blah blah) /boot/System.map -> System.map-2.4.18-3
# ls -l /boot/System.map-2.4.18-3
-rw-r--r-- (blah blah) 465966 Apr 18 2002 /boot/System.map-2.4.18-3
Now, here's the weird part...the symbol is defined in the symbol table.
It appears to be the correct symbol table. All looks right in the world.
Could the cpu arch have anything to do with it...some 486/586/686
#define maybe?
So? What am I missing? ...Anyone? Anyone?...Bueller?
Thanks in advance.
--
Gary Cote
Transat Technologies
-
: 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
