Ubuntu
ndiswrapper package

ndiswrapper-dkms 1.60-3~ubuntu16.04.1: ndiswrapper kernel module failed to build

Bug #1709214 reported by rodney on 2017-08-08

This bug report is a duplicate of: Bug #1608744: ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build [gcc: error: unrecognized command line option '-fstack-protector-strong']. Edit Remove

This bug affects 1 person

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

Bug Description

installed upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ndiswrapper-dkms 1.60-3~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
DKMSKernelVersion: 4.4.0-89-generic
Date: Sat Aug 5 18:28:06 2017
DuplicateSignature: dkms:ndiswrapper-dkms:1.60-3~ubuntu16.04.1:gcc: error: unrecognized command line option ‘-fstack-protector-strong’
InstallationDate: Installed on 2017-07-09 (29 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
PackageVersion: 1.60-3~ubuntu16.04.1
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.60-3~ubuntu16.04.1: ndiswrapper kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

rodney (rodchr423) wrote on 2017-08-08:

DKMSBuildLog.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (8.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (949 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2017-08-08

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2017-08-08:

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