Re: Unresolved symbols

[David Daney <ddaney@avtrex.com>]

David Kesselring wrote:

> I've been unabled to track down these errors. I think it's because I don't
> understand how some of the linux h files are used by an independently
> compiled kernel module. Why is "extern __inline__" used in a file like
> atomic.h.
> If any of you have any pointers on the following errors, I'd appreciate
> your comments.
> /lib/modules/2.4.22/kernel/net/pcifvnet.o: unresolved symbol
> atomic_sub_return
> /lib/modules/2.4.22/kernel/net/pcifvnet.o: unresolved symbol __udelay
> /lib/modules/2.4.22/kernel/net/pcifvnet.o: unresolved symbol atomic_add
> /lib/modules/2.4.22/kernel/net/pcifvnet.o: unresolved symbol strcpy
> /lib/modules/2.4.22/kernel/net/pcifvnet.o: unresolved symbol atomic_sub
>  
Often if you don't compile with optimization turned on you get things 
like this.  You have to compile with optimization set high enough to get 
inlining enabled.

David Daney.