[MacPorts] #36910: Virtualbox @4.2.4 +vde2+vnc won't start VMs

[MacPorts]

#36910: Virtualbox @4.2.4 +vde2+vnc won't start VMs
---------------------------+--------------------------------
  Reporter:  and.damore@…  |      Owner:  macports-tickets@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.2
Resolution:                |   Keywords:
      Port:  virtualbox    |
---------------------------+--------------------------------

Comment (by and.damore@…):

 Replying to [comment:12 royliu@…]:
 > Just to be clear, does this mean the problem has to be in one of
 {{{cctools, cctools-headers, ld64}}}? {{{apple-gcc42}}} didn't seem to
 change.

 Yes the problem is on of those ports. Specifically it's been introduced
 with changeset:99185, I can obtain a working virtualbox from an updated
 dports tree by reverting devel/cctools devel/cctools-headers and
 devel/ld64 to r99184 and I can obtain a broken virtualbox by then updating
 those three ports at r99185.

 Since apple-gcc42 is built using cctools > ld64 > cctools-headers I
 rebuilt apple-gcc42 as well on each test run in order to have a clean room
 test.

 Have a try with
 {{{
 sudo port unload virtualbox
 sudo port -f uninstall virtualbox-guest-additions virtualbox-extension-
 pack virtualbox apple-gcc42 cctools ld64 cctools-headers
 cd /opt/local/var/macports/sources/svn.macports.org/trunk/dports
 svn up
 svn up -r 99184 devel/cctools devel/ld64 devel/cctools-headers
 sudo port -s install cctools-headers ld64 cctools apple-gcc42 virtualbox
 }}}

 That's roughly the script I've been using for test, edit your paths and
 variants accordingly.

-- 
Ticket URL: <https://trac.macports.org/ticket/36910#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS