Virtualbox @4.2.14: failed to determine Darwin version

[mkae (Marko Käning)]

Virtualbox' build system cannot handle Mavericks yet:

:info:configure Checking for environment: Determined build machine: darwin.amd64, target machine: darwin.amd64, OK.
:info:configure Checking for kBuild: found, OK.
:info:configure Checking for Darwin version:   failed to determine Darwin version. (uname -r: 13.0.0)
:info:configure Check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.o
rg_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16/configure.log for d
etails
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16" && ./configure --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/opt/local/bin/gcc-apple-4.2 --with-g++=/opt/local/bin/g++-apple-4.2 --enable-vde --enable-vnc
:info:configure Exit code: 1
:error:configure org.macports.configure for port virtualbox returned: configure failure: command execution failed
:debug:configure Error code: NONE

[ryandesign (Ryan Carsten Schmidt)]

We should try updating the port to the latest version. If that still doesn't work, then this problem should be reported the developers of virtualbox.

[mkae (Marko Käning)]

I agree. Thanks for hinting out this ticket.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #41414.

[ktaylor1024@…]

Cc Me!

[dony@…]

THis also fails for me. I've seen a version of the failing script for this ticket here : ​https://www.virtualbox.org/svn/vbox/trunk/configure

An entry is lacking in the "case" instruction in function "check_darwinversion()" to take into account that uname now returns 13.

cheers Christophe

---

Replying to mk@…:

Virtualbox' build system cannot handle Mavericks yet:

:info:configure Checking for environment: Determined build machine: darwin.amd64, target machine: darwin.amd64, OK.
:info:configure Checking for kBuild: found, OK.
:info:configure Checking for Darwin version:   failed to determine Darwin version. (uname -r: 13.0.0)
:info:configure Check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.o
rg_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16/configure.log for d
etails
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16" && ./configure --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/opt/local/bin/gcc-apple-4.2 --with-g++=/opt/local/bin/g++-apple-4.2 --enable-vde --enable-vnc
:info:configure Exit code: 1
:error:configure org.macports.configure for port virtualbox returned: configure failure: command execution failed
:debug:configure Error code: NONE

[sam.halliday@…]

Cc Me!

[sam.halliday@…]

still no joy :-(

[cooljeanius (Eric Gallager)]

Cc Me!

[eddieh (Eddie Hillenbrand)]

Has anyone tried patching the the configure script? Does anyone know if there is a ticket in the VirtualBox bug tracker corresponding to this issue? If a ticket exists in their system, I can't seem to find it.

[akimd (Akim Demaille)]

Cc Me!

[gamperl@…]

Cc Me!

[kpreid (Kevin Reid)]

Cc Me!

[t-remke@…]

Cc Me!

[joel@…]

Please reference ​https://forums.virtualbox.org/viewtopic.php?f=31&t=44590.

I looked at the configure script, and noticed the following starting at line 1999: check_darwinversion() { ... You'll see a case statement that matches each kernel release. It looks like they have some simple code to select the proper SDK from Xcode that is used while compiling. It should be trivial to add a statement for kernel 13 and point to the proper developer SDK.

I'm not very macports savvy, so I'm not sure how to make a patch and submit it, or even what the proper way to test my theory in the build system so that macports will successfully install the package or I'd just do it all and put a patch on this ticket.

[joel@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #43565. As stated previously in this ticket, somebody needs to try updating the port to the current version, and please submit a diff of that. If that still doesn't work on Mavericks, then please file a bug report with the developers of VirtualBox.

[acmeprocessgroup@…]

Sorry to keep persisting about this bug, but it appears the fix to allow virtualbox to install via ports is still not working. The VirtualBox people have read the reports here and have checked the two most recent VirtualBox releases .. they work.

So not sure who is responsible, but I think everyone who has reproduced and reported this problem would appreciate having it fixed pronto.

[cooljeanius (Eric Gallager)]

Replying to acmeprocessgroup@…:

The VirtualBox people have read the reports here and have checked the two most recent VirtualBox releases .. they work.

Link to where they said this?

[pixilla (Bradley Giesbrecht)]

Replying to acmeprocessgroup@…:

So not sure who is responsible

The virtualbox port is nomaintainer so no one is responsible and patches are always welcome.

[66Ton99 (Ton Sharp)]

Cc Me!

[posita (Matt Bogosian)]

Cc Me!

[markemer (Mark Anderson)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #47045.

[lord@…]

Cc Me!

[nbasanes@…]

I get the following error for installing virtualbox:

The output for the failed configure failure follows:

$ sudo port install virtualbox
Password:
--->  Computing dependencies for virtualbox
--->  Configuring virtualbox
Error: org.macports.configure for port virtualbox returned: configure failure: command execution failed
Please see the log file for port virtualbox for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port virtualbox failed

I also got the following results from the log file:

​http://0bin.net/paste/RtIXLCPaxH7CMori#vSlC+GribhUjK6D5sZjoja+v0cS0OyMDBksEJOMXvhy

The above link expires in one month from this post, but the following line from the log stood out to me:

info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16" && ./configure --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/opt/local/bin/gcc-apple-4.2 --with-g++=/opt/local/bin/g++-apple-4.2 --enable-vde --enable-vnc

Replying to mk@…:

Virtualbox' build system cannot handle Mavericks yet:

:info:configure Checking for environment: Determined build machine: darwin.amd64, target machine: darwin.amd64, OK.
:info:configure Checking for kBuild: found, OK.
:info:configure Checking for Darwin version:   failed to determine Darwin version. (uname -r: 13.0.0)
:info:configure Check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.o
rg_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16/configure.log for d
etails
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16" && ./configure --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/opt/local/bin/gcc-apple-4.2 --with-g++=/opt/local/bin/g++-apple-4.2 --enable-vde --enable-vnc
:info:configure Exit code: 1
:error:configure org.macports.configure for port virtualbox returned: configure failure: command execution failed
:debug:configure Error code: NONE

[nbasanes@…]

, This looks like a case of a missing or out of date build dependency, to me.

[WolfgangFahl (Wolfgang Fahl)]

With El Capitan the problem persists:

Checking for Darwin version: failed to determine Darwin version. (uname -r: 15.2.0)

this patch improves the darwin check 2003a2004,2009

15\.*)

darwin_ver="10.11" # El Capitan sdk="xcode-select -print-path/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk" CXX_FLAGS="-mmacosx-version-min=10.7 -isysroot $sdk -Wl,-syslibroot,$sdk" ;;

now i get qt4 not found ...

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #51160. See also #40786 and #50622 proposing updates to the port.

[essandess (Steve Smith)]

CC me.

[ooogwayduh-rock (Van L)]

Before the second attempt to 'sudo port install virtualbox', the call to 'port clean' results in the following:

$ port clean
Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/ooogwayduh-rock").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.

$ sudo port clean
Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/ooogwayduh-rock").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.

$ sudo -H -u root port clean 
Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/ooogwayduh-rock").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.

2018-02-09 has VirtualBox/5.2.6 platform packages at

https://www.virtualbox.org/wiki/Downloads

Looks like the virtualbox/4.2.16 release is no longer available.

⋮
⋮
⋮

:debug:main Executing org.macports.main (virtualbox)
:debug:main dropping privileges: euid changed to 502, egid changed to 501.
:debug:archivefetch archivefetch phase started at Fri Feb  9 11:10:48 AEDT 2018
:msg:archivefetch --->  Fetching archive for virtualbox
:debug:archivefetch Executing org.macports.archivefetch (virtualbox)
:debug:archivefetch euid/egid changed to: 0/0
:debug:archivefetch chowned /opt/local/var/macports/incoming to macports
:debug:archivefetch euid/egid changed to: 502/501
:info:archivefetch --->  virtualbox-4.2.16_1+vde2+vnc.darwin_15.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch --->  Attempting to fetch virtualbox-4.2.16_1+vde2+vnc.darwin_15.x86_64.tbz2 from http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/virtualbox
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch virtualbox-4.2.16_1+vde2+vnc.darwin_15.x86_64.tbz2 from https://packages.macports.org/virtualbox
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch virtualbox-4.2.16_1+vde2+vnc.darwin_15.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/virtualbox
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:fetch fetch phase started at Fri Feb  9 11:10:49 AEDT 2018
:notice:fetch --->  Fetching distfiles for virtualbox
:debug:fetch elevating privileges for fetch: euid changed to 0, egid changed to 0.
:debug:fetch dropping privileges: euid changed to 502, egid changed to 501.
:debug:fetch Executing org.macports.fetch (virtualbox)
:info:fetch --->  VirtualBox-4.2.16.tar.bz2 does not exist in /opt/local/var/macports/distfiles/virtualbox
:notice:fetch --->  Attempting to fetch VirtualBox-4.2.16.tar.bz2 from http://download.virtualbox.org/virtualbox/4.2.16
:debug:fetch Privilege de-escalation not attempted as not running as root.
:debug:checksum checksum phase started at Fri Feb  9 11:12:05 AEDT 2018
:notice:checksum --->  Verifying checksums for virtualbox
:debug:checksum Executing org.macports.checksum (virtualbox)
:info:checksum --->  Checksumming VirtualBox-4.2.16.tar.bz2
:debug:checksum Calculated (rmd160) is a49d044f6935199a71f6bdf94fd9082f9888d2d6
:debug:checksum Correct (rmd160) checksum for VirtualBox-4.2.16.tar.bz2
:debug:checksum Calculated (sha256) is ff0f8916d039120554d9d73c7cae1863d6161933374374ec2f5313892046d45a
:debug:checksum Correct (sha256) checksum for VirtualBox-4.2.16.tar.bz2
:debug:checksum Privilege de-escalation not attempted as not running as root.
:debug:extract extract phase started at Fri Feb  9 11:12:06 AEDT 2018
:notice:extract --->  Extracting virtualbox
:debug:extract setting option extract.cmd to /usr/bin/bzip2
:debug:extract Executing org.macports.extract (virtualbox)
:info:extract --->  Extracting VirtualBox-4.2.16.tar.bz2
:debug:extract setting option extract.args to '/opt/local/var/macports/distfiles/virtualbox/VirtualBox-4.2.16.tar.bz2'

⋮
⋮
⋮

:info:configure Check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16/configure.log for details
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.16" && ./configure --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/opt/local/bin/gcc-apple-4.2 --with-g++=/opt/local/bin/g++-apple-4.2 --enable-vde --enable-vnc 
:info:configure Exit code: 1
:error:configure Failed to configure virtualbox: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_emulators_virtualbox/virtualbox/main.log for details.

Nothing seems to happen for 'uninstall'.

$ sudo port uninstall virtualbox

[kencu (Ken)]

The version of VirtualBox available on MacPorts is several years out of date. We should probably delete it soon if nobody is prepared to update it.

Looks like it's a pain to build it, as it can't use current tools and significant manual steps are needed to set up the build environment.

I would vote we just delete the VirtualBox port as it's frustrating people who think it should work.

Installing the binary is pretty much the only practical way to get VirtualBox on MacOS these days.

[ooogwayduh-rock (Van L)]

Docker Toolbox installs VirtualBox as part of its run.

​https://github.com/docker/toolbox/releases

Perhaps, packages known to be broken and years out of date should stop early automatically with an informative message and alternatives.

And, anyone curious to fix that package has the choice to force install then see how they go.

[kencu (Ken)]

feel free to reopen if you feel otherwise.