Re: Re: 2.4.20; unresolved symbols

On Fri, 12 Sep 2003, Avin Sigurani wrote:

> > Unresolved symbols problems, such as the message
> > above, occur when you
> > are trying to install a module built for the wrong
> > kernel

> As I have said, I am in fact compiling against the
> runing kernel.  Just in case, the first time you
> suggested that this was the problem, I recompiled the
> various kernels I was using.  Before I compile the
> modules, I reboot into the kernel I want and change
> the symbolic link "linux" in /usr/src to point to the
> source tree of the running kernel.  

Read the first few lines of the 'make' output -- that will tell you what
header file set it is using.

Here is how you can find the module symbol version numbers:
   For the running kernel
      more /proc/ksyms
   The information for the kernel header files is in a file that looks like
      more /usr/src/linux-2.4.21-6_Scyld/include/linux/modules/
   The compiled module info may be viewed with
      nm module.o

> So, the problem is something else.  Perhaps it has to
> do with the libraries I am using?

No, the C library doesn't come into play here.

> or the compiler?

A few Red Hat distribution shipped with two compilers, but the Makefile
checks for that.  ("Uhmmm, yeah, we want you to change everything to use
this new compiler, but it's got a problem with compiling the kernel.")


-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993