[SOLVED] app-emulation/virtualbox-4.3.38 emerge fails

Markus09 · Tux's lil' helper Joined: 22 Mar 2013 Posts: 78

Hello!

I tried to emerge virtualbox, but it fails with

Jaglover · Posted: Fri Jan 06, 2017 3:12 am Post subject:

Try again with MAKEOPTS=-j1 and pastebin the whole log.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

Markus09 · Tux's lil' helper Joined: 22 Mar 2013 Posts: 78

MAKEOPTS=-j1 is/was already active.

make.conf: http://pastebin.com/zD1SHXfS
build.log: https://paste.pound-python.org/show/9ZoBVbatZLS1Fz6OUVkL/

davydm · n00b Joined: 06 Jan 2017 Posts: 73

Not to just be a "me too", but I get the exact same error; interesting part is at line 97 in the pastebin link:

/var/tmp/portage/app-emulation/virtualbox-4.3.38/work/VirtualBox-4.3.38/out/linux.amd64/release/obj/VBoxDD/vboxssdt-cpuhotplug.hex.pre 35: Device (SCKL) { Name (_HID, "ACPI0004") Name (_UID, "SCKCPUL") Processor (CPUL, 0x15, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name (_UID, "SCKL-CPU0") Name (_PXM, 0x00) Method(_MAT, 0) { Name (APIC, Buffer (

{0x00, 0x08, 0x15, 0x15}) IF (CPCK(0x15))
[*** iASL: Very long input line, message below refers to column 451 ***]
Error 6058 - Invalid type ([Processor] found, Store operator requires [Integer|String|Buffer|Package|DebugObject|Reference])

Just for chuckles, I tried basically disabling most USE flags and still got the same.

I'm quite new to Gentoo, shifted after 16 years of Debian, so please excuse me if I'm doing something wrong; the output from emerge requests certain information and here are the pastebins:

http://pastebin.com/bJz5Rw7a
http://pastebin.com/EHenPXzh
http://pastebin.com/DATwKXV8
http://pastebin.com/7k4rQ3mp

Anything else I can provide to debug?

Jaglover · Posted: Fri Jan 06, 2017 9:36 pm Post subject:

Net search returned same error with same version of VirtualBox ... when building on FreeBSD. I think you should file a bug.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

davydm · n00b Joined: 06 Jan 2017 Posts: 73

I'm happy to do so -- bearing in mind again that I'm a gentoo n00b, so this may sound like a stupid question: should I be filing a bug upstream, at virtualbox? Or a gentoo bug against the package? I wanted to see if perhaps installing a testing package would have this problem already resolved, so according to https://packages.gentoo.org/packages/app-emulation/virtualbox, there's a 4.3.40 version of virtualbox, however, doing:

Markus09 · Tux's lil' helper Joined: 22 Mar 2013 Posts: 78

I emerged =app-emulation/virtualbox-5.1.12 with ~amd64, which caused a few rebuilds and only two additional keyword changes for the virtualbox-modules and kbuild.
This builds just fine with USE flags:

davydm · n00b Joined: 06 Jan 2017 Posts: 73

@Markus09 thanks for the package.keywords tip; as a n00b, I don't understand why ACCEPT_KEYWORDS="~amd64" didn't work cleanly for the 4.3.30 package (and I apparently didn't try it without a version specifier, as it does work that way:/). I would have popped it in package.keywords if the environment variable had worked, but o well... I think I did try the same without a version specifier and also had havoc -- I must have been doing something Just Plain Wrong somewhere :/

However, I'd rather have the latest-latest vbox anyways, so this works out just fine for me.

Since there are available binaries for virtualbox 4.3.38 (virtualbox-bin installs fine), that would suggest that virtualbox can build at this version with the correct configuration -- so is that still not an ebuild error? Again, please bear with my n00bness.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

When you set ACCEPT_KEYWORDS in the environment, that acceptance works for everything Portage considers during that run of emerge, not just for the package(s) that you named on the command line. This was equivalent to setting it in /etc/portage/make.conf, other than that the latter would apply for every run until you edited the file again, whereas environment overrides apply only until you unset the variable.

When you specify keywords in /etc/portage/package.accept_keywords, the keyword applies only to the package named (and respects version restrictions, if you use those). Your attempt at the command line approved both a ~amd64 virtualbox (which you wanted) and updating any supporting packages to ~amd64 if Portage decided to consider updating those packages. When you use the file, Portage may still consider updating supporting packages, but it can only update them within the constraints of the keywords you approved for those supporting packages. Assuming no environment variable and no other relevant entries in package.accept_keywords, any supporting packages can only be updated to stable versions, not testing versions.

C5ace · Posted: Tue Jan 10, 2017 11:52 am Post subject:

I have the same problem. app-emulation/virtualbox-4.3.38 fails compile on new install and fails recompile on 3 existing installations which where made a long time ago and updated on 12 Dec. 2016 to virtualbox-4.3.38.

Build log shows:

davydm · n00b Joined: 06 Jan 2017 Posts: 73

artbody · Guru Joined: 15 Sep 2006 Posts: 489 Location: LB

with the ~amd64 option you pull in development-versions this is like > unstable on debian
for some packages this my work but if you set it in the make.conf global results in unstable Gentoo

thats why you should do this in /etc/portage/portage.keywords
_________________
Never give up
WM : E16 the true enlightenment
achim

Hu · Moderator Joined: 06 Mar 2007 Posts: 21635

C5ace · Posted: Thu Jan 12, 2017 12:17 am Post subject:

Problem solved:

Build.log says when building app-emulation/virtualbox-4.3.38 STABLE:

DX94 · n00b Joined: 12 Jan 2017 Posts: 2

Markus09 · Tux's lil' helper Joined: 22 Mar 2013 Posts: 78

Thank you all for your helpful responses!
Thread marked as solved.