>this is not a gcc bug. this is an ubuntu management specific arrogance
(and perhaps some cash from redmond with love) - of course it is
completely wrong to patch the kernel makefile because they decided to
ship a gcc unable to build the kernel itself (with wrong
defaults/specs). but like they said repeatedly, they are not a
democracy. also just like linus said repeatedly, fuck unubuntu!

ok thanks for you really nice and well proven point.

AFAICT also Fedora and other major linux distros are starting enabling pie by 
default, and probably more will come.

Unfortunately I don't want to answer why you are wrong, because I don't
want to feed the troll, and you didn't say anything worth an answer in
your post.

So, the answer will be generic to other people (who probably have more clues 
than you on the reasons).
pie is a security flag that is really important for an OS. Unfortunately asking 
maintainers to enable it resulted in not many adaptions, and many critical 
pieces of software without such hardening flag enabled.
Enabling by default in gcc sounded a better idea, and the side effect has been 
that virtualbox/kernel had to disable it manually to still build.

For this reason -f-no-pie has been created, and it should work with no issues.
And this bug/flag has been injected and the kernel is now fixed, so please move 

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.

  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
Status in gcc-defaults package in Ubuntu:
Status in linux package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)


  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:

  This has been firstly reported against a nvidia crash:

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
   /dev/snd/controlC1:  oem        2014 F.... pulseaudio
   /dev/snd/pcmC0D0p:   oem        2014 F...m pulseaudio
   /dev/snd/controlC0:  oem        2014 F.... pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
   eth0      no wireless extensions.

   eth1      no wireless extensions.

   lo        no wireless extensions.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware                            1.157

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to