Failed to emerge app-emulation/virtualbox-guest-additions-5.2.6 Some of the errors: /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.6/work/vboxguest/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); emerge --info '=app-emulation/virtualbox-guest-additions-5.2.6::gentoo' https://paste.pound-python.org/show/Gp0iPBjcxaLEGTNEieQ3/ emerge -pqv '=app-emulation/virtualbox-guest-additions-5.2.6::gentoo' https://paste.pound-python.org/show/jEtz6eHsSp9iTuPZYFdn/ /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.6/temp/build.log https://paste.pound-python.org/show/BJyIBWSu51AhVWdQVrlu/ /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.2.6/temp/environment https://paste.pound-python.org/show/cotF0DZNQEkKHFpLfBBr/
Working solution at https://forums.gentoo.org/viewtopic-p-8177550.html#8177550
The patch posted in the forum link by @fedeliallalinea works but you have to apply it manually because eapply_user is called with current directory is set to S. The patch needs one level below S. What is Gentoo convention for the current directory before calling eapply_user? There was discussion about this subject here: https://forums.gentoo.org/viewtopic-t-1056914-start-0.html
On possibility is to change the ebuild near the end of src_prepare() function to cd directory to WORKDIR before applying the patch. pushd "${WORKDIR}" &>/dev/null || die eapply "${FILESDIR}"/vbox-guest-additions-kernel-4.15.patch popd &>/dev/null || die eapply_user }
(In reply to email200202 from comment #0) > Failed to emerge app-emulation/virtualbox-guest-additions-5.2.6 > > Some of the errors: Please *attach* all relevant files to this bug report.
Jeroen Roovers, please see the first post. All the files are included there as links. Please also check the forum discussion. https://forums.gentoo.org/viewtopic-p-8177550.html#8177550 I attached the patch file and modified ebuild.
Created attachment 518058 [details, diff] vbox-guest-additions-kernel-4.15.patch
Created attachment 518060 [details] virtualbox-guest-additions-5.2.6.ebuild
Created attachment 518062 [details, diff] ebuild diff
Upstream commits https://www.virtualbox.org/changeset/70624/vbox https://www.virtualbox.org/changeset/70625/vbox
What are we waiting for?
After kernel update, the ebuild change and the patch are not enough to get virtualbox-guest-additions to emerge. You need to define KERN_VER variable. KERN_VER="4.15.4" emerge -av1 app-emulation/virtualbox-guest-additions Otherwise, it will fail with error KERN_DIR not defined.
(In reply to email200202 from comment #11) > After kernel update, the ebuild change and the patch are not enough to get > virtualbox-guest-additions to emerge. You need to define KERN_VER variable. > > KERN_VER="4.15.4" emerge -av1 app-emulation/virtualbox-guest-additions > > Otherwise, it will fail with error KERN_DIR not defined. This still seems to be the case with virtualbox-guest-additions-5.2.14. Not sure how this is building for anyone without that env variable.
The bug is still there and you have to set KERN_VER to get it to build. And it is "UNCONFIRMED"!
I cannot reproduce this issue, works fine here.
(In reply to email200202 from comment #13) > The bug is still there and you have to set KERN_VER to get it to build. And > it is "UNCONFIRMED"! For KERN_VER see also https://bugs.gentoo.org/680296
