Portage 2.3.103 (python 3.6.11-final-0, default/linux/amd64/17.1/desktop/plasma, gcc-9.3.0, glibc-2.30-r8, 5.7.6-gentoo-x86_64 x86_64) sys-devel/gcc-9.3.0-r1 Kernel: 5.7.6-gentoo app-emulation/virtualbox-modules-6.1.12 test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) cc1: error: incompatible gcc/plugin versions cc1: error: fail to initialize plugin ./scripts/gcc-plugins/stackleak_plugin.so cc1: error: incompatible gcc/plugin versions cc1: error: fail to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so make[3]: *** [scripts/Makefile.build:267: /var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv/linux/SUPDrv-linux.o] Error 1 make[3]: *** Waiting for unfinished jobs.... Reproducible: Always
Created attachment 650126 [details] emerge log
Created attachment 650128 [details] emerge info
FYI on a Portage 3.0.0 (python 3.7.8-final-0, default/linux/amd64/17.1/desktop/gnome/systemd, gcc-10.2.0, glibc-2.31-r6, 5.7.10-gentoo x86_64) system i get similar results, with the following differences (Module.symvers link creation error, no gcc plugin errors) & additional info >>> Compiling source in /var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work ... ln: failed to create symbolic link 'Module.symvers': File exists * Preparing vboxdrv module make -j24 -l24 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' CC=x86_64-pc-linux-gnu-gcc KERN_DIR=/usr/src/linux KERN_VER=5.7.10-gentoo O=/usr/src/linux V=1 KBUILD_VERBOSE=1 all === Building 'vboxdrv' module === make[1]: Entering directory '/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv' make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /usr/src/linux M=/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv SRCROOT=/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv -j24 modules make[2]: Entering directory '/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv' make[2]: warning: -j24 forced in submake: resetting jobserver mode. test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make[2]: *** [Makefile:703: include/config/auto.conf] Error 1 make[2]: Leaving directory '/usr/src/linux-5.7.10-gentoo' make[1]: *** [/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv/Makefile-footer.gmk:117: vboxdrv] Error 2 make[1]: Leaving directory '/var/tmp/portage/app-emulation/virtualbox-modules-6.1.12/work/vboxdrv' make: *** [Makefile:58: vboxdrv] Error 2 * ERROR: app-emulation/virtualbox-modules-6.1.12::gentoo failed (compile phase): * emake failed Files are, however, not missing; # file include/generated/autoconf.h include/config/auto.conf include/generated/autoconf.h: Linux make config build file, ASCII text, with very long lines include/config/auto.conf: Linux make config build file, ASCII text, with very long lines # ls -l include/generated/autoconf.h include/config/auto.conf -rw-r----- 1 root root 43231 Jul 25 10:12 include/config/auto.conf -rw-r----- 1 root root 58804 Jul 25 10:12 include/generated/autoconf.h
i had this issue some time ago to. make sure you have the kernel and the module compiled using the same version of gcc. for me the cause was the kernel was compiled using older gcc and i was attempting to compile the module using newer gcc.
I can confirm that it was indeed the GCC version in my case. After recompiling the kernel, the modules could be emerged without problems.
Yes, this was exactly what happen.
