Date: Wed, 27 Aug 2003 10:07:45 -0700
From: Stephen Hemminger <shemminger@osdl.org>
To: LGW <large@lilymarleen.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: porting driver to 2.6, still unknown relocs... :(
Message-Id: <20030827100745.0d944f33.shemminger@osdl.org>
In-Reply-To: <1061999977.22825.71.camel@dhcp23.swansea.linux.org.uk>
References: <3F4CB452.2060207@lilymarleen.de>
	<20030827081312.7563d8f9.rddunlap@osdl.org>
	<3F4CCF85.1020502@lilymarleen.de>
	<1061999977.22825.71.camel@dhcp23.swansea.linux.org.uk>
Organization: Open Source Development Lab
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1060
Lines: 26

On 27 Aug 2003 16:59:38 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Mer, 2003-08-27 at 16:34, LGW wrote:
> > The driver is mostly a wrapper around a generic driver released by the 
> > manufacturer, and that's written in C++. But it worked like this for the 
> > 2.4.x kernel series, so I think it has something todo with the new 
> > module loader code. Possibly ld misses something when linking the object 
> > specific stuff like constructors?
> 
> The new module loader is kernel side, it may well not know some of the
> C++ specific relocation types. 

You did something that was explicitly not supported on 2.4 and it worked,
it broke on 2.6.

The fact that it worked it all on 2.4 was a fluke.

It's time to breakdown, do the right thing and figure out how to rewrite/translate the
C++ code to C.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/