[Pkg-lirc-maint] Bug#429249: lirc-modules-source: Badly documented, doesn't work

Joseph Thomas-Kerr joetk at elec.uow.edu.au
Sun Jul 29 22:56:52 UTC 2007

I think I can shed some further light on the subject.

I'm running sarge, and have built my own kernel from linux-source-2.6.15,  
which is unzipped into /usr/src/linux-source-2.6.15.

I installed lirc-modules-source, and unzipped the resulting gz file to  
/usr/src, which left me with /usr/src/modules/lirc.

When I first run "debian/rules binary-modules", I get "sed: can't read  
/usr/src/linux/2.6.15/build/include/linux/version.h: No such file or  
directory" so I create the following directories and symlinks:

/usr/src/linux/2.6.15 -> ../linux-source-2.6.15
/usr/src/linux/2.6.15/build/include -> ../include

Then, running rules again, I get "sed: can't read  
/usr/src/linux/include/linux/version.h: No such file or directory", so I  
create another symlink

/usr/src/linux/include ->../linux-source-2.6.15/include

and then the module is built correctly and works just fine.

IMO there are two things broken here:

1. most importantly, despite the broken compile session, the installer  
still generates a broken deb file, after which which many users (including  
nathaniel and myself) won't realise that there is a problem and happily  
install the package.

2. lirc seems to expect a different kernel source tree structure than the  
one debian provides. It would be great if the lirc package on debian is  
configured to work with the debian kernel sources out of the box.


More information about the Pkg-lirc-maint mailing list