From: David Daney <ddaney@avtrex.com>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Unresolved symbols
Date: Tue, 28 Oct 2003 10:31:59 -0800 [thread overview]
Message-ID: <3F9EB61F.8010906@avtrex.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0310281308450.20592-100000@ares.mmc.atmel.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.
next prev parent reply other threads:[~2003-10-28 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 18:12 Unresolved symbols David Kesselring
2003-10-28 18:31 ` David Daney [this message]
2003-10-28 18:53 ` Jan-Benedict Glaw
2003-10-28 20:36 ` Geert Uytterhoeven
2003-10-28 21:18 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F9EB61F.8010906@avtrex.com \
--to=ddaney@avtrex.com \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox