Re: How to build only linux-image-2.6.18-6-686
On Sat, Jun 07, 2008 at 09:35:28PM +0000, Tzafrir Cohen wrote:
> On Sat, Jun 07, 2008 at 05:23:19PM -0400, Lennart Sorensen wrote:
> > On Sat, Jun 07, 2008 at 08:31:47PM +0000, Tzafrir Cohen wrote:
> > > My problem with make-kpkg has always been that I could never rely on its
> > > generated -headers packages to actually work.
> > Odd, the headers it generated allways worked for me.
> Taken to another system?
> The problems I remember:
> 1. the "source" and "build" links pointed to an incorrect place. An
> invalid build link is a problem.
How are you trying to build the modules? If you build everything in the same
kernel-source-dir$ fakeroot make-kpkg kernel-image modules-image
should also (along with the desired kernel image) build modules unpacked in
dirs under /usr/src/modules. Note that this and procedures below *will only
work* for Debian packaged modules source packages.
If you just have the headers package available, you can try (adapted from an
ancient README.ftape I found here, replace ftape with the relevant module,
some things may not be up to date)
* If you are not using make-kpkg and have kernel headers package installed:
You really do not need to have full kernel sources installed to build
the modules, having the kernel headers package that was used to build
the kernel is enough. In this case,
1) Go to the ftape root directory (/usr/src/modules/ftape in
the ftape-source package).
2) Run as root something like
debian/rules KVERS=2.4.22-1 KSRC=/usr/src/kernel-headers-2.4.22-1 \
adapted to your kernel version (KVERS), location (KSRC), and
As Lennart pointed out, make-kpkg and linux-source*.deb is the preferred way
to go for end users. However, the second way should also work. If the
modules source package is ready for module-assistant a third possibility is
open, but I never used it.
I insist that nothing of the above will be useful if you try to build
modules directly from upstream sources.
Hope this helps