# BUG IMPACT:
Module fails FTBFS in lucid rendering oss4 unusable, fix at least allows the modules to build
# DEVELOPMENT BRANCH FIX:
oss4-4.2-build2003 dkms.conf in maverick uses /lib/modules/${kernelver}/build/include/linux/limits.h, this is the fix backported, currently lucid version uses /lib/modules/${kernelver}/source/include/linux/limits.h
# MINIMAL PATCH
oss4_4.2-build2002-2ubuntu0.1.debdiff attached to end of bug report
# TEST CASE
$ sudo apt-get install oss4-dkms
Building module:
cleaning build area....
cp /lib/modules/2.6.35-22-generic/source/include/linux/limits.h /var/lib/dkms/oss4/4.2-build2002/build/core && make -C /lib/modules/2.6.35-22-generic/build SUBDIRS=/var/lib/dkms/oss4/4.2-build2002/build/core modules && make -C /var/lib/dkms/oss4/4.2-build2002/build/drivers osscore_symbols.inc && make -C /lib/modules/2.6.35-22-generic/build SUBDIRS=/var/lib/dkms/oss4/4.2-build2002/build/drivers modules....(bad exit status: 1)
Error! Bad return status for module build on kernel: 2.6.35-22-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/oss4/4.2-build2002/build/ for more information.
0
0
dpkg: error processing oss4-dkms (--install):
subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
oss4-dkms
nb: 2.6.35 kernel in example but verified broken on 2.6.32 lucid kernels too
# REGRESSION POTENTIAL:
The package is unusable as the module fails to build. Problems that could be caused by actually using the oss4 modules
are unknown but certainly possible
********** ORIGINAL MESSAGE **********
After running an update to a new kernel I got an error about packacge oss4-dkms. I ignored it, alas, and rebooted the next day. After reboot, all sound was gone. Indeed, no modules for sound were loaded. I remembered the error and forced a reinstall:
apt-get --reinstall install oss4-base oss4-dkms
This went wrong when installing oss4-dkms: it tried to update the new kernel (2.6.32-23-generic on 10.04 x64) to include the oss4 modules but couldn't proceed since /lib/modules/2.6.32-23-generic/source/ doesn't exist. I checked, kernel sources are installed. A simple ln -s /usr/src/linux-headers-2.6.32-23-generic/ /lib/modules/2.6.32-23-generic/source solved the problem.
Proposed solution: either have the oss4-dms package look in /usr/src/linux-headers-xxx for it's files, or create the symlink given above by default.
This problem is caused by an inconsistency in the linux-headers packages.
Some of them provide the symlink, some other don't.
The latest oss4-dkms package (4.2build3002-1) now explicitely requires a linux-header package to be installed, which should fix the problem is most cases.
In general, I am not sure that pointing to /usr/src/... is a good solution, the existence of a /lib/modules/`uname -r`/build symlink is a pretty standard requirement for generic module build so this problem will happen again for other external modules and I would recommend investigating why this symlink does not exist in some installs...