Bug 646468 – app-emulation/virtualbox-guest-additions-5.2.6 with kernel 4.15.0 - ?

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description email200202 2018-02-03 07:55:03 UTC]

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/

[Comment 1 Marco Genasci 2018-02-03 12:23:02 UTC]

Working solution at https://forums.gentoo.org/viewtopic-p-8177550.html#8177550

[Comment 2 email200202 2018-02-04 04:55:39 UTC]

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

[Comment 3 email200202 2018-02-04 05:15:51 UTC]

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
}

[Comment 4 Jeroen Roovers (RETIRED) 2018-02-05 16:45:25 UTC]

(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.

[Comment 5 email200202 2018-02-06 08:05:54 UTC]

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.

[Comment 6 email200202 2018-02-06 08:07:06 UTC]

Created attachment 518058 [details, diff]
vbox-guest-additions-kernel-4.15.patch

[Comment 7 email200202 2018-02-06 08:07:56 UTC]

Created attachment 518060 [details]
virtualbox-guest-additions-5.2.6.ebuild

[Comment 8 email200202 2018-02-06 08:34:54 UTC]

Created attachment 518062 [details, diff]
ebuild diff

[Comment 9 Marco Genasci 2018-02-06 11:08:00 UTC]

Upstream commits
https://www.virtualbox.org/changeset/70624/vbox
https://www.virtualbox.org/changeset/70625/vbox

[Comment 10 email200202 2018-02-19 08:49:17 UTC]

What are we waiting for?

[Comment 11 email200202 2018-02-19 09:38:18 UTC]

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.

[Comment 12 Josh Williams 2018-10-09 14:30:56 UTC]

(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.

[Comment 13 email200202 2018-10-13 03:05:33 UTC]

The bug is still there and you have to set KERN_VER to get it to build. And it is "UNCONFIRMED"!

[Comment 14 Viorel Munteanu 2022-11-09 14:13:33 UTC]

I cannot reproduce this issue, works fine here.

[Comment 15 Viorel Munteanu 2022-11-11 10:02:18 UTC]

(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