Not a member yet? Why not Sign up today
Create an account  

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 
XanMod 4.15.0,1 'file missing' building Virtualbox Guest Additions 5.2.6,7 [solved]

#1
Error and some warnings while building Virtualbox Guest Additions modules:

Code:
Building the main Guest Additions module.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.15.0-xanmod1/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
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)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/5/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -fno-var-tracking-assignments -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.15.0-xanmod1/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE  -DKBUILD_BASENAME='"VBoxGuest_linux"'  -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c
In file included from ./include/linux/module.h:18:0,
                 from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:88,
                 from /tmp/vbox.0/VBoxGuest-linux.c:36:
/tmp/vbox.0/VBoxGuest-linux.c:1165:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:35: note: (near initialization for ‘__param_ops_log.set’)
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1165:63: note: (near initialization for ‘__param_ops_log.get’)
 module_param_call(log,            vgdrvLinuxParamLogGrpSet,   vgdrvLinuxParamLogGrpGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:35: note: (near initialization for ‘__param_ops_log_flags.set’)
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1166:63: note: (near initialization for ‘__param_ops_log_flags.get’)
 module_param_call(log_flags,      vgdrvLinuxParamLogFlagsSet, vgdrvLinuxParamLogFlagsGet, NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:35: note: (near initialization for ‘__param_ops_log_dest.set’)
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:63: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1167:63: note: (near initialization for ‘__param_ops_log_dest.get’)
 module_param_call(log_dest,       vgdrvLinuxParamLogDstSet,   vgdrvLinuxParamLogDstGet,   NULL, 0664);

                                                               ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:35: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:35: note: (near initialization for ‘__param_ops_r3_log_to_host.set’)
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                   ^
./include/linux/moduleparam.h:233:24: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                        ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:66: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                                                  ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
/tmp/vbox.0/VBoxGuest-linux.c:1173:66: note: (near initialization for ‘__param_ops_r3_log_to_host.get’)
 module_param_call(r3_log_to_host, vgdrvLinuxParamR3LogToHostSet, vgdrvLinuxParamR3LogToHostGet, NULL, 0664);

                                                                  ^
./include/linux/moduleparam.h:233:37: note: in definition of macro ‘module_param_call’
   { .flags = 0, .set = _set, .get = _get };  \
                                     ^
cc1: some warnings being treated as errors
scripts/Makefile.build:316: fallo en las instrucciones para el objetivo '/tmp/vbox.0/VBoxGuest-linux.o'
make[2]: *** [/tmp/vbox.0/VBoxGuest-linux.o] Error 1
Makefile:1508: fallo en las instrucciones para el objetivo '_module_/tmp/vbox.0'
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:101: fallo en las instrucciones para el objetivo 'vboxguest'
make: *** [vboxguest] Error 2
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.

I'm not sure if the cause is from Xanmod or from Virtualbox itself, however some info about "invalid kernel configuration" is shown:

Code:
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 ;
"(...) the grandest occasion the past or present has seen, or the future can hope to see." -- Cervantes.
Reply

#2
Problem still persists with 4.15.1-xanmod2.
Virtualbox future update to discard, perhaps?
BTW thank you @roberto for reporting.

Code:
$ uname -a
Linux 4.15.1-xanmod2 #1 SMP PREEMPT Sun Feb 4 18:44:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Code:
Building the main Guest Additions module.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.15.1-xanmod2/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
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)

(05-02-2018, 08:43 PM)tropic Wrote: Problem still persists with 4.15.1-xanmod2.
Waiting for Virtualbox upcoming update.
Thank you @roberto for reporting.
(...)

Edit: @roberto, the problem is for sure not related to XanMod kernel, same problem found with latest Ubuntu mainline kernel.
Also the problem is found with Ubuntu 16.04 LTS default kernel, Ubuntu 16.04 HWE latest kernel and XanMod 4.14 series.
I will work later to learn more about this issue because it also affects XanMod itself.
"(...) the grandest occasion the past or present has seen, or the future can hope to see." -- Cervantes.
Reply

#3
- Virtualbox Guest Additions 5.2.4 works with all recent kernels but 4.15.x series.
- Virtualbox Guest Additions 5.2.6 and 5.2.7 don't work whatever the kernel. 

Confirmed solution for the main problem post at this thread:
- Downgrade to Virtualbox 5.2.4 and Virtualbox extended pack 5.2.4.
"(...) the grandest occasion the past or present has seen, or the future can hope to see." -- Cervantes.
Reply



[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Forum Jump:


Users browsing this thread:
1 Guest(s)