Ubuntu
dahdi-linux package

dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build

Bug #1179326 reported by Júlio César on 2013-05-13

This bug report is a duplicate of: Bug #1133658: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build [wctdm.c:2587:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘wctdm_init_one’]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	dahdi-linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

I was trying install packages for Virtual Box, so i open synaptic and make download all dkms. Sorry my english, i am from Brasil

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11
Uname: Linux 3.8.0-20-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.8.0-20-generic
Date: Sun May 12 21:05:10 2013
InstallationDate: Installed on 2013-03-22 (51 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1:2.5.0.1+dfsg-1ubuntu2
SourcePackage: dahdi-linux
Title: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build
UpgradeStatus: Upgraded to raring on 2013-04-25 (17 days ago)

Tags:

Revision history for this message

Júlio César (caipiravirtual) wrote on 2013-05-13:

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

Apport retracing service (apport) on 2013-05-13

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-06-05:

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 1133658, 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.