Ubuntu
broadcom-sta package

broadcom-sta-dkms failed to build with kernel 3.11.0-7-generic

Bug #1228456 reported by knorr on 2013-09-21

This bug report is a duplicate of: Bug #1227900: broadcom-sta-dkms 5.100.82.112-11: broadcom-sta kernel module failed to build [error: implicit declaration of function ‘create_proc_entry’]. Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	broadcom-sta (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Build log attached

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: broadcom-sta-dkms 5.100.82.112-11
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Sat Sep 21 09:44:13 2013
InstallationDate: Installed on 2013-09-19 (1 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
LANGUAGE=ru
TERM=xterm
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

knorr (a-sokolov) wrote on 2013-09-21:

make.log Edit (3.1 KiB, text/plain)
Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")

summary:

- broadcom-sta-dkmsvfailde to build with kernel 3.11.0-7-generic
+ broadcom-sta-dkms failed to build with kernel 3.11.0-7-generic

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-19:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in broadcom-sta (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-09-02:

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