* Tony Houghton [100111 21:00 +0000] [...] > m-a should be able to find the headers automatically. It certainly knows > all about the headers-*-common and headers-*-arch packages because it > downloads them if they aren't already installed. I think the problem is > because the alsa package finds the headers in some way of its own (I'm > not used to module packages having configure scripts) that isn't > compliant with debian kernels, but I can't find docs about how you're > supposed to prepare kernel module debs. I checked /lib/modules/... and > found these links, HTH:
Yeah, could please do as follows: cd /usr/src rm -rf modules tar -xjf alsa-driver.tar.bz cd /usr/src/modules cat /path/to/alsa-source-rules.patch | patch -p1 cd /usr/src tar -cjf alsa-driver.tar.bz modules and run your m-a build again? alsa-source-rules.patch is attached. Should work now. Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-)
diff -Naurd a/alsa-driver/debian/rules b/alsa-driver/debian/rules --- a/alsa-driver/debian/rules 2009-09-26 03:18:26.000000000 +0200 +++ b/alsa-driver/debian/rules 2010-01-16 14:55:01.000000000 +0100 @@ -42,8 +42,6 @@ # Use updates/ subdirectory so that the modules in alsa-modules-$KVERS # are given priority (by depmod) over modules under kernel/. CONFIGURE_OPT = --prefix=/usr \ - --with-kernel=$(KSRC) \ - --with-build=$(KSRC) \ --with-moddir=/lib/modules/$(KVERS)/updates/alsa \ --with-sequencer=yes
signature.asc
Description: Digital signature
