linux-mips
[Top] [All Lists]

Re: Unresolved symbols

To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Unresolved symbols
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 28 Oct 2003 22:18:29 +0100
Cc: David Kesselring <dkesselr@mmc.atmel.com>, Linux/MIPS Development <linux-mips@linux-mips.org>
In-reply-to: <Pine.GSO.4.21.0310282135290.10351-100000@waterleaf.sonytel.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.GSO.4.44.0310281308450.20592-100000@ares.mmc.atmel.com> <Pine.GSO.4.21.0310282135290.10351-100000@waterleaf.sonytel.be>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Tue, Oct 28, 2003 at 09:36:05PM +0100, Geert Uytterhoeven wrote:
> Date: Tue, 28 Oct 2003 21:36:05 +0100 (MET)
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> To: David Kesselring <dkesselr@mmc.atmel.com>
> cc: Linux/MIPS Development <linux-mips@linux-mips.org>
> Subject: Re: Unresolved symbols
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> 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.

I've replaced all extern inline in cvs 2.4 / 2.6.

  Ralf

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