"Steven W. Orr" wrote:
>
> Ok. I'll try this one. Modules are frequently written to be tied into
> certain kernel structures which are very dependent on a particular rev of
> the kernel. In case a module is not dependent on a particular version of a
> kernel, you can compile your modules with the feature "Set version
> information on all symbols for modules" set to no.
>
> Is this my final answer? Well Regis, it is but I'm only about 80%
> sure. Can someone confirm?
>
> On Sun, 8 Oct 2000, Kenneth E. Lussier wrote:
>
> =>All,
> =>
> =>Is there any way to compile modules so that they are portable from one
> =>kernel version to another? I would like to build modules on one system
> =>and be able to insert them into /lib/modules/kernel-rev and have them
> =>actually work (demanding, ain't I? ;-). I'd like to have a fairly broad
> =>spectrum of kernel choices. It would be nice if the modules could work
> =>with *ANY* 2.2.x kernel. However, I have a hard time compiling for one
> =>minor version and going to another (i.e compiling for 2.2.14 and using
> =>with a 2.2.16).
> =>
> =>I know that there is a kernel option to set kernel module info that is
> =>*SUPPOSED* to do this, but it never seems to work for me.
> =>
> =>TIA,
> =>Kenny
>
According to the help on "make menuconfig" you want to set the
variable CONFIG_MODVERSIONS to Y to make the modules semi-portable
(within the 2.2 series, not from 2.2 to 2.4). According to the help,
you have to be sure you have the program "genksyms" or the build will
fail if CONFIG_MODVERSIONS=Y.
jeff
--
jeff smith
---------------------------------------------------------------------------------
thought for the day: To have died once is enough.
-- Publius Vergilius Maro (Virgil)
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
