| To: | David Kesselring <dkesselr@mmc.atmel.com> |
|---|---|
| Subject: | Re: Unresolved symbols |
| From: | Geert Uytterhoeven <geert@linux-m68k.org> |
| Date: | Tue, 28 Oct 2003 21:36:05 +0100 (MET) |
| Cc: | Linux/MIPS Development <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 |
| Sender: | linux-mips-bounce@linux-mips.org |
On Tue, 28 Oct 2003, 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.
`extern inline' is wrong, and should be replaced by `static inline', which is
work-in-progress.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | BCM1250 Current Descriptor, Gilad Benjamini |
|---|---|
| Next by Date: | Re: Unresolved symbols, Ralf Baechle |
| Previous by Thread: | Re: Unresolved symbols, Jan-Benedict Glaw |
| Next by Thread: | Re: Unresolved symbols, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |