if (static_branch_unlikely(&mcsafe_key)) ^~~~~~~~~~~~~~~~~~~~~~ /lib/modules/4.9.6-gentoo/build/include/linux/jump_label.h:295:65: error: ‘__builtin_types_compatible_p’ was not declared in this scope if (!__builtin_types_compatible_p(typeof(*x), struct static_key) && \ ^ /lib/modules/4.9.6-gentoo/build/include/linux/compiler.h:168:42: note: in definition of macro ‘unlikely’ ----------------------------------------------------------------- This is an unstable amd64 chroot image (named hardened-unstable_20170120-150937) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * llvm-config --version: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2: -----------------------------------------------------------------
Created attachment 461712 [details] emerge-info.txt
Created attachment 461714 [details] app-emulation:virtualbox-guest-additions-5.1.14:20170128-124418.log.bz2
Created attachment 461716 [details] emerge-history.txt
Created attachment 461718 [details] environment
Created attachment 461720 [details] etc.portage.tbz2
The same.
Same here
Same problem here.
Created attachment 464366 [details, diff] Fix sloppy printk
Created attachment 464368 [details, diff] C++ version of __READ_ONCE
With the two patches just uploaded( Fix sloppy printk, C++ version of __READ_ONCE) and this diff to the ebuild: --- a/virtualbox-guest-additions-5.1.14.ebuild 2017-02-19 19:38:41.490542701 +0100 +++ b/virtualbox-guest-additions-5.1.14.ebuild 2017-02-19 18:01:54.032052975 +0100 @@ -122,7 +122,8 @@ MAKE="kmk" \ emake TOOL_YASM_AS=yasm \ VBOX_ONLY_ADDITIONS=1 \ - KBUILD_VERBOSE=2 + KBUILD_VERBOSE=2 \ + CXXFLAGS="-fpermissive -D__builtin_types_compatible_p\(x,y\)=1" it builds. Don't know it it works, can anyone confirm?
Oops, wrong bug, should have been: https://bugs.gentoo.org/show_bug.cgi?id=603472 I do think this is close to your problem too.
*** This bug has been marked as a duplicate of bug 603472 ***