Re: porting driver to 2.6, still unknown relocs... :(

["Richard B. Johnson" <root@chaos.analogic.com>]

On Wed, 27 Aug 2003, Stephen Hemminger wrote:

> 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.
>

> You did something that was explicitly not supported on 2.4 and it worked,
                             ^^^^^^^^^^^^^^^^^^^^^^^^_______ Yes!

There was lots of discussion/flames back-and-forth with newbies
requiring that modules be written in C++.  This is what you get.
Some of the C++ built-ins are not even global so the linker
won't be able to find them if they are used. It's not just
a matter of emulating 'new'. Parameter-passing 'by reference' also
won't work so putting 'C' wrappers around stuff like they do
in Dr. Jobbs and C/C++ Journal isn't going to work inside
the kernel where there is no support.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (794.73 BogoMips).
            Note 96.31% of all statistics are fiction.