[Top] [All Lists]

Re: Unresolved symbols

Subject: Re: Unresolved symbols
From: Jan-Benedict Glaw <>
Date: Tue, 28 Oct 2003 19:53:33 +0100
In-reply-to: <>
Original-recipient: rfc822;
References: <> <>
User-agent: Mutt/1.5.4i
On Tue, 2003-10-28 10:31:59 -0800, David Daney <>
wrote in message <>:
> 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.

Right. Once again, if you compile modules outside the kernel, please:

        Use exactly the GCC parameters that are used by in-kernel-tree
                        compiled modules!


   Jan-Benedict Glaw    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

Attachment: signature.asc
Description: Digital signature

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