nvidia-375 375.39-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build

[Kunal Tyagi]

Occured while upgrading using ```$sudo apt upgrade```

---
Setting up nvidia-375 (375.39-0ubuntu0.16.04.1) ...
update-alternatives: warning: alternative /usr/lib/nvidia-367-prime/ld.so.conf (part of link group x86_64-linux-gnu_gl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367/ld.so.conf (part of link group x86_64-linux-gnu_gl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367-prime/ld.so.conf (part of link group x86_64-linux-gnu_egl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367/ld.so.conf (part of link group x86_64-linux-gnu_egl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367-prime/alt_ld.so.conf (part of link group i386-linux-gnu_gl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367/alt_ld.so.conf (part of link group i386-linux-gnu_gl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367-prime/alt_ld.so.conf (part of link group i386-linux-gnu_egl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: alternative /usr/lib/nvidia-367/alt_ld.so.conf (part of link group i386-linux-gnu_egl_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/i386-linux-gnu_egl_conf is dangling; it will be updated with best choice
update-alternatives: using /usr/lib/nvidia-375/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in auto mode
update-alternatives: warning: alternative /usr/share/nvidia-367/glamor.conf (part of link group glamor_conf) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/glamor_conf is dangling; it will be updated with best choice
update-alternatives: using /usr/share/nvidia-375/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode
INFO:Enable nvidia-375
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Loading new nvidia-375-375.39 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-67-generic
Building for architecture x86_64
Building initial module for 4.4.0-67-generic

Error! Bad return status for module build on kernel: 4.4.0-67-generic (x86_64)
Consult /var/lib/dkms/nvidia-375/375.39/build/make.log for more information.
Setting up nvidia-367 (375.39-0ubuntu0.16.04.1) ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-375 375.39-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
DKMSKernelVersion: 4.4.0-67-generic
Date: Thu Mar 23 08:59:18 2017
DuplicateSignature: dkms:nvidia-375:375.39-0ubuntu0.16.04.1:./arch/x86/include/asm/arch_hweight.h:58:7: error: expected absolute expression
InstallationDate: Installed on 2016-12-08 (104 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageVersion: 375.39-0ubuntu0.16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: nvidia-graphics-drivers-375
Title: nvidia-375 375.39-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Kunal Tyagi (kunal-tyagi-3-1994)]

Adding the relevant log file

[Daniel van Vugt (vanvugt)]

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