package blcr-dkms 0.8.2-15ubuntu1 failed to install/upgrade: blcr kernel module failed to build

[Marlon Moura]

I have the same error over and over again on a 64bit Natty persistent live cd:

Terminal output:

Configurando blcr-dkms (0.8.2-15ubuntu1) ...

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=2.6.38-8-generic -C /lib/modules/2.6.38-8-generic/build M=/var/lib/dkms/blcr/0.8.2/build.........................(bad exit status: 2)

Error! Bad return status for module build on kernel: 2.6.38-8-generic (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/blcr/0.8.2/build/ for more information.
0
0

-------
The end of the file /var/lib/dkms/blcr/0.8.2/build/make.log:

======================================================================
Please review the following configuration information:
  Kernel source directory = /lib/modules/2.6.38-8-generic/build
  Kernel build directory = /lib/modules/2.6.38-8-generic/build
  Kernel symbol table = /boot/System.map-2.6.38-8-generic
  Kernel version probed from kernel build = 2.6.38-8-generic
  Kernel running currently = 2.6.38-8-generic
======================================================================
cd /var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/ && env -i PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/usr/sbin:/sbin:/usr/lib/dkms make prepare
cd /var/lib/dkms/blcr/0.8.2/build/blcr_imports/kbuild/ && env -i PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/usr/sbin:/sbin:/usr/lib/dkms make prepare
touch /var/lib/dkms/blcr/0.8.2/build/prepare-stamp
echo "BLCR_IMPORT_SOURCES := blcr_imports/kbuild/" > /var/lib/dkms/blcr/0.8.2/build/module_files
echo "BLCR_SOURCES := cr_module/kbuild/" >> /var/lib/dkms/blcr/0.8.2/build/module_files
  LD /var/lib/dkms/blcr/0.8.2/build/built-in.o
  LD /var/lib/dkms/blcr/0.8.2/build/blcr_imports/kbuild/built-in.o
  CC [M] /var/lib/dkms/blcr/0.8.2/build/blcr_imports/kbuild/imports.o
  CC [M] /var/lib/dkms/blcr/0.8.2/build/blcr_imports/kbuild/module.o
  LD [M] /var/lib/dkms/blcr/0.8.2/build/blcr_imports/kbuild/blcr_imports.o
  LD /var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/built-in.o
  CC [M] /var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.o
/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.c: In function ‘vmadump_thaw_proc’:
/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.c:1092: error: ‘struct signal_struct’ has no member named ‘count’
/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.c: In function ‘vmadump_freeze_proc’:
/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.c:1999: error: ‘struct signal_struct’ has no member named ‘count’
make[2]: ** [/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild/vmadump_common.o] Erro 1
make[1]: ** [/var/lib/dkms/blcr/0.8.2/build/cr_module/kbuild] Erro 2
make: ** [_module_/var/lib/dkms/blcr/0.8.2/build] Erro 2
make: Saindo do diretório `/usr/src/linux-headers-2.6.38-8-generic'

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: blcr-dkms 0.8.2-15ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 29 00:46:23 2011
ErrorMessage: blcr kernel module failed to build
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu1
SourcePackage: blcr
Title: package blcr-dkms 0.8.2-15ubuntu1 failed to install/upgrade: blcr kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

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 853735, 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. Feel free to continue to report any other bugs you may find.