On Thu, 2006-08-31 at 15:27 +0200, Michael Prokop wrote:
> > Do you have a build log? One from a manual or module-assistant build
> > would do.
>
> Sure, see attached buildlog.
Thanks
> > I only tested with m-a against a Debian kernel package. I'll try against
> > a self built kernel now.
>From the looks of the log this is the cause.
The kernel.org build system does depmod after install but the
linux-headers package supplied by Debian doesn't. The depmod creates
those extra files and the package blindly includes them.
Are you in a position to try this simple patch as a fix? If it works
I'll roll a new package tonight and request an upload from my sponsor.
Index: debian/rules
===================================================================
--- debian/rules (revision 108)
+++ debian/rules (working copy)
@@ -159,6 +159,7 @@
$(KMAKE) -C i2c-drivers
$(KMAKE) -C driver install DESTDIR=$(CURDIR)/debian/$(PKGNAME)
$(KMAKE) -C i2c-drivers install DESTDIR=$(CURDIR)/debian/$(PKGNAME)
+ rm debian/$(PKGNAME)/lib/modules/*/modules.*
dh_installmodules
dh_installdocs
dh_installchangelogs
> In case this might be important (it often is when kernel source
> packages are broken):
>
> Do you build the package against the currently running kernel?
> Because I'm building the module against a kernel version which does
> not match the currently running one.
I do this occasionally and it seems to work fine.
Ian.
--
Ian Campbell
Current Noise: Annihilator - Word Salad
Q: How do you catch a unique rabbit?
A: Unique up on it!
Q: How do you catch a tame rabbit?
A: The tame way!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
