Ubuntu
blcr package

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

Bug #962956 reported by nic-stange on 2012-03-23

This bug report is a duplicate of: Bug #804943: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	blcr (Ubuntu)	New	Undecided	Unassigned

Bug Description

Not sure if this ir related to https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/804943

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: blcr-dkms
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.2.0-20-generic
Date: Fri Mar 23 11:00:15 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-14 (8 days ago)

Tags:

Revision history for this message

nic-stange (nic-stange) wrote on 2012-03-23:

DKMSBuildLog.txt Edit (6.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (778 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (6.0 KiB, text/plain; charset="utf-8")

Revision history for this message

nic-stange (nic-stange) wrote on 2012-03-23:

According to DKMSBuildLog.txt, it actually is a dup, sorry!

Apport retracing service (apport) on 2012-03-23

tags:

removed: need-duplicate-check

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2012-03-23:

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.