Messages in this thread | | | Subject | Re: ANN: LKMB (Linux Kernel Module Builder) version 0.1.16 | Date | Sat, 18 Jan 2003 23:37:19 +0100 | From | Olaf Titz <> |
| |
> > Use "/lib/modules/`uname -r`/build" as a default kernel directory, but > > allow it to be overridden somehow from the command line. Then do something > > like... >... > Do you mean I'll need a live Linux kernel to build the kernel module > package?
Whoever invented this /lib/modules/... scheme should have known that it provokes this sort of misunderstandings, not to mention is broken in other ways too.
You need the _source_ of the kernel the module will run on to compile modules. You don't need to _run_ this kernel while compiling. Putting build infrastructure into a deployment directory at the least causes confusion, not to mention that the deployment directory might not even exist on the development machine. (I routinely compile kernels and modules of different configurations for three boxes on one of them, the other two don't even have a complete development toolset.)
Compiling modules is one of the things which always have been among the most broken things in the kernel build systems, can this please be fixed and properly documented?
Olaf
- 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/
| |