Summary: | app-emulation/virtualbox-modules-4.3.28: compile phase fails when it tries to create /lib/modules/4.1.1/build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tka <tka> |
Component: | [OLD] Unspecified | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | bkohler, nerevar101, patrick |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tka
2015-07-01 14:11:44 UTC
I suspect this is related to bug 553670 where there the kernel claiming to be 4.1.1 is actually 4.1 (aka 4.1.0), do you see this same issue on 4.1.0? (In reply to Ben Kohler from comment #1) > I suspect this is related to bug 553670 where there the kernel claiming to > be 4.1.1 is actually 4.1 (aka 4.1.0), do you see this same issue on 4.1.0? No, this is a real 4.1.1 kernel (from kernel.org, not portage). The build also fails for a 4.0.5 kernel. I don't know the build system for virtualbox-modules and what it really does here, but I find the message "cannot create directory ‘/lib/modules/4.1.1’" suspicious. The compile phase should not (try to) create directories in that location. I don't know what's going on here but this is what made me suspect the 4.1 vs 4.1.1 issue: make[2]: Entering directory '/usr/src/linux-4.1' Are your sources in /usr/src/linux-4.1.1/ fully configured & built? Can you try "make modules_install" again from /usr/src/linux-4.1.1/ ? (In reply to Ben Kohler from comment #3) > I don't know what's going on here but this is what made me suspect the 4.1 > vs 4.1.1 issue: > > make[2]: Entering directory '/usr/src/linux-4.1' Despite the name, that is the correct directory for my 4.1.1 sources. > Are your sources in /usr/src/linux-4.1.1/ fully configured & built? Can you > try "make modules_install" again from /usr/src/linux-4.1.1/ ? My sources are in /usr/src/linux-4.1 (linux-4.1.tar plus patch-4.1.1). Completely build and installed. /lib64/modules/4.1.1 exists (and contains the modules). Reinstalling the modules does not help. Looking at the changelog, this issue may be fallout from 14 Jun 2015; Michał Górny <mgorny@gentoo.org> virtualbox-modules-4.3.18.ebuild, virtualbox-modules-4.3.26.ebuild, virtualbox-modules-4.3.28.ebuild: Fix build with objtree!=srctree, bug #285866. https://github.com/gentoo /gentoo-portage-rsync-mirror/pull/150 by nE0sIghT. That would also explain why it worked in early June, but fails now. (In reply to tka from comment #4) > Looking at the changelog, this issue may be fallout from > Fix build with objtree!=srctree, bug #285866. Confirmed. Revision 1.3 of the ebuild works and 1.4 fails. Ok, I figured it out. Portage needs x-permission for the directory /lib/modules/4.1.1, which it did not have on my system. chmod o+x /lib/modules/4.1.1 fixed the problem and virtualbox-modules was build without problem.
Interestingly, the emerge output did not indicate that problem:
> * Found kernel object directory:
> * /lib/modules/4.1.1/build
Maybe a check for the required permissions can be added to the ebuild/eclass.
FYI, this is no longer an issue in the 5.0.x series. |