On Tue, Jul 30, 2002 at 09:00:04PM +1200, Chris Hellyar wrote:
> You'll have to download the entire source tree for the kernel, and do
> a './configure' (and pick the right things...) and then a 'make
> modules'.
Don't you mean ``make {menu,old,x}config''?
If it's a standalone source tree for the module, you may only need the
correct kernel headers. If the module is integrated with the kernel
source tree, you'll need the whole kernel source tree.
When building the module, make sure the .config is as close to the
running 2.2.21 kernel config as possible -- otherwise the module may
fail to load with unresolved symbols, or may load and silently trash
your kernel.
> Assuming you're using the same glibc & gcc version it'll all work when
> you copy the module across...
The version of glibc you're running won't make a difference. The kernel
is not linked with glibc.
Differing versions of gcc, binutils, and modutils may affect your
ability to load the module on the target machine after building it.
Section 8.7 of the lkml FAQ has some useful information about building
modules: http://www.tux.org/lkml/#s8-7
--
Matthew Gregan |/
/| [EMAIL PROTECTED]
