Re: unresolved symbols cropping up in a previously working driver.

From: Keith Owens (kaos@ocs.com.au)
Date: Fri Jun 09 2000 - 21:58:23 EDT

Next message: Philipp Rumpf: "Re: Oops report on microcode.o linux-2.4.0-test1-ac11"

Previous message: Jeff Dike: "Re: Running Untrusted Code in a Restricted Process"
In reply to: ronbarry@es.com: "unresolved symbols cropping up in a previously working driver."
Next in thread: Alan Cox: "Re: unresolved symbols cropping up in a previously working driver."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, 9 Jun 2000 19:46:32 -0600 ,
ronbarry@es.com wrote:
>hello.o: unresolved symbol printk

Sounds like you compiled the kernel with symbol versions but compiled
the module without versions.

nm hello.o | grep printk
grep printk /proc/ksyms

I bet you see something like 'printk_Rsmp_1b7d4074' in ksyms and just
'printk' in hello.o.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Philipp Rumpf: "Re: Oops report on microcode.o linux-2.4.0-test1-ac11"
Previous message: Jeff Dike: "Re: Running Untrusted Code in a Restricted Process"
In reply to: ronbarry@es.com: "unresolved symbols cropping up in a previously working driver."
Next in thread: Alan Cox: "Re: unresolved symbols cropping up in a previously working driver."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Jun 09 2000 - 22:03:26 EDT