linux-mips
[Top] [All Lists]

Re: Unresolved symbols

To: David Kesselring <dkesselr@mmc.atmel.com>
Subject: Re: Unresolved symbols
From: David Daney <ddaney@avtrex.com>
Date: Tue, 28 Oct 2003 10:31:59 -0800
Cc: linux-mips@linux-mips.org
In-reply-to: <Pine.GSO.4.44.0310281308450.20592-100000@ares.mmc.atmel.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.4.44.0310281308450.20592-100000@ares.mmc.atmel.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
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.


<Prev in Thread] Current Thread [Next in Thread>