package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
blcr (Ubuntu) |
Fix Released
|
Undecided
|
Alan |
Bug Description
blcr does not build against the linux-rt kernel (which is at 2.6.31-10 as of up-to-date lucid installed from alpha 3), complaining that symbol __put_task_struct has not been defined.
If I am not mistaken, this causes dkms to refuse to automatically build other modules - please correct me if I'm wrong. I've had to invoke dkms manually to compile the nvidia binary driver support module, and I assume that the cause of this problem was the failure to compile blcr in the first place.
I suppose this may be hard to fix if blcr relies on features specific to 2.6.32, given that the only alternative to make compilation work would be to forward-port the rt patch to 2.6.32. In the past this has been problematic -- Intrepid and Jaunty had broken linux-rt packages which wouldn't work on more than one CPU core, besides other issues.
Would it be possible to blacklist blcr from being compiled against the -rt kernel? Does anything in the standard desktop install of lucid depend on having a working blcr?
ProblemType: Package
Architecture: amd64
Date: Mon Mar 8 04:25:41 2010
DistroRelease: Ubuntu 10.04
ErrorMessage: blcr kernel module failed to build
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
Package: blcr-dkms 0.8.2-9
PackageArchitec
PackageVersion: 0.8.2-9
ProcVersionSign
SourcePackage: blcr
Title: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build
Uname: Linux 2.6.31-10-rt x86_64
Related branches
tags: | added: patch |
Changed in blcr (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Alan Woodland (awoodland) |
Changed in blcr (Ubuntu): | |
status: | In Progress → Fix Committed |
BLCR can in theory build against almost any standard 2.6.X kernel. I have no idea what -rt changes internally though. Do you have a config.log from the failed configure attempt that you could attach to this report?
As for nvidia modules not getting built because of this I'd say that was a bug with dkms itself. There's no inherent reason why failure of one module should prevent another one from getting built. The boot time script that causes these to get built is pretty simple from what I remember.
Alan