[Pkg-mol-commits] r63 - mol/trunk/debian

[Gaudenz Steinlin]

Author: gaudenz
Date: 2006-10-02 21:43:57 +0000 (Mon, 02 Oct 2006)
New Revision: 63

Modified:
   mol/trunk/debian/changelog
   mol/trunk/debian/mol-modules-source.README.Debian
Log:
update documentation on building kernel modules



Modified: mol/trunk/debian/changelog
===================================================================
--- mol/trunk/debian/changelog	2006-10-02 20:17:11 UTC (rev 62)
+++ mol/trunk/debian/changelog	2006-10-02 21:43:57 UTC (rev 63)
@@ -32,6 +32,7 @@
   * document new upstream location in copyright
   * revert changes in 0.9.71~pre9 to ablk.c as they cause a hang on boot
   * change build system of mol-modules-source to use kbuild
+  * update documentation on building kernel modules
 
   [ Aurélien GÉRÔME ]
 
@@ -42,7 +43,7 @@
   * Add Swedish debconf templates translation (sv.po), thanks to Daniel
     Nylander <yeager at lidkoping.net>. (Closes: #340974)
 
- -- Gaudenz Steinlin <gaudenz at debian.org>  Mon,  2 Oct 2006 21:58:19 +0200
+ -- Gaudenz Steinlin <gaudenz at debian.org>  Mon,  2 Oct 2006 23:43:12 +0200
 
 mol (0.9.70-20.1) unstable; urgency=low
 

Modified: mol/trunk/debian/mol-modules-source.README.Debian
===================================================================
--- mol/trunk/debian/mol-modules-source.README.Debian	2006-10-02 20:17:11 UTC (rev 62)
+++ mol/trunk/debian/mol-modules-source.README.Debian	2006-10-02 21:43:57 UTC (rev 63)
@@ -32,27 +32,17 @@
   package, this also creates a .changes file which you can sign with
   the debsign command.
 
-* Compiling the modules with kernellab
+* A note on kernel headers and kernel build system
 
-  If you are using kernellab, there is no need to unpack the source
-  for the modules.  Simply create a symbolic link from the gzipped tar
-  archive to wherever the @MODULES entry in your kernellab
-  configuration file points to (usually ~/kernellab/modules or
-  /var/state/kernellab/modules).  The command `kernellab <host>
-  <version> mol-modules' will then build a Debian package for the
-  modules.
-
-* A note on kernel headers
-
   Whichever of the above methods you choose, building the modules
-  requires kernel headers.  There is no need to worry about this if
-  you are using make-kpkg or kernellab, because they simply use the
-  header files from the kernel source.  When compiling the modules
-  manually with make, it is probably easiest to use the headers from
-  the appropriate kernel-headers package.  For that reason, the
-  Makefiles expect the headers in the directory
-  /usr/src/kernel-headers-<your kernel version>.  If you keep your
-  kernel headers in a different place, change the KERNEL_HEADERS
-  variable in the Rules.make file.
+  requires kernel headers and the kernel build system.  There is 
+  no need to worry about this if you are using make-kpkg, because
+  they simply use the header files from the kernel source.  When
+  compiling the modules manually with make, it is probably easiest
+  to use the headers from the appropriate linux-headers package.
+  For that reason, the Makefiles expect the headers in the directory
+  /lib/modules/<your kernel version>-<flavour>/build which usually
+  is a symlink to the kernel headers.  If you keep your kernel headers
+  in a different place, you need to set the KSRC variable.
 
- -- Jens Schmalzing <jensen at debian.org> 14 Aug 2001
+ -- Gaudenz Steinlin <gaudenz at debian.org> 02 Oct 2006