Ubuntu
linux package

  1. Bug #1556676
  2. Comment #27

Comment 27 for bug 1556676

Revision history for this message
Richard Elkins (texadactyl) wrote :

Please note that if a build has an issue installing 100%, then the reporter should not proceed with a test.

I thought that I observed a totally successful install of the 4.5 kernel image and headers yesterday but I missed seeing that the make of bcmwl failed to make even though the installation was successful according to the final state of the repository:

ii linux-headers-4.5.0-040500 4.5.0-040500.20160314013 all Header files related to Linux kernel version 4.5.0
ii linux-headers-4.5.0-040500-generic 4.5.0-040500.20160314013 amd64 Linux kernel headers for version 4.5.0 on 64 bit x86 SMP
ii linux-image-4.5.0-040500-generic 4.5.0-040500.20160314013 amd64 Linux kernel image for version 4.5.0 on 64 bit x86 SMP

Logs are attached in a tar.gz file. Specifically, gcc version 4:4.8.2-1ubuntu6 (up-to-date for 14.04.04) flagged the make of bcmwl as follows:

make: Entering directory `/usr/src/linux-headers-4.5.0-040500-generic'
Makefile:666: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  LD /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/built-in.o
  CC [M] /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.o
gcc: error: unrecognized command line option ‘-fstack-protector-strong’
make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.o] Error 1
make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build] Error 2
make: Leaving directory `/usr/src/linux-headers-4.5.0-040500-generic'

It looks like I would need (at least) an upstream `gcc` to match this kernel. Who knows what else? This might be like peeling an onion.

Keep in mind that my work-around described above is solid. Being a developer, I understand that the kernel developers need to prioritize their time and effort. If the kernel development team would be more comfortable with my retesting under 16.04 (would make sense!), then I can wait until this machine is available for an upgrade in, roughly, one month.