blcr-dkms 0.8.2-15ubuntu2: blcr kernel module failed to build

[zeimusu]

This bug appeared during apt-get dist-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: blcr-dkms 0.8.2-15ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.0-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.2.0-21-generic
Date: Fri Mar 30 21:01:13 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu2
SourcePackage: blcr
Title: blcr-dkms 0.8.2-15ubuntu2: blcr kernel module failed to build
UpgradeStatus: Upgraded to precise on 2012-03-18 (12 days ago)

[zeimusu (james-kilfiger)]

Errors pasted below:

Setting up blcr-dkms (0.8.2-15ubuntu2) ...

Creating symlink /var/lib/dkms/blcr/0.8.2/source ->
                 /usr/src/blcr-0.8.2

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.2.0-19-generic -C /lib/modules/3.2.0-19-generic/build M=/var/lib/dkms/blcr/0.8.2/build.....(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-3.2.0-19-generic is not supported
Error! Bad return status for module build on kernel: 3.2.0-19-generic (x86_64)
Consult /var/lib/dkms/blcr/0.8.2/build/make.log for more information.

and here is the line from make.log

configure: error: --with-linux argument '3.2.0-19-generic' is neither a kernel version string nor a full path
make[1]: *** [/var/lib/dkms/blcr/0.8.2/build/config-stamp] Error 1
make: *** [_module_/var/lib/dkms/blcr/0.8.2/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.2.0-19-generic'

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 804943, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.