[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:  reopened
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.2
Resolution:                |   Keywords:
      Port:  virtualbox    |
---------------------------+--------------------------------

Comment (by msa@…):

 Replying to [comment:28 and.damore@…]:
 > Replying to [comment:27 msa@…]:
 > > I just uninstalled ld64, llvm, cctools and all of my macports gcc
 compilers and reinstalled virtualbox. It still doesn't work, but one
 relevant fact I noticed is that when I ran "sudo port install
 name:virtualbox" macports didn't reinstall ld64 or any build tools.
 Indeed,
 > >
 > > {{{
 > > $ port deps virtualbox
 > > Full Name: virtualbox @4.2.6_1+vde2+vnc
 > > Build Dependencies:   pkgconfig
 > > Library Dependencies: qt4-mac, curl, libidl, libxml2, libxslt,
 openssl, libsdl,
 > >                       vde2, LibVNCServer
 > > $ port installed ld64 apple-gcc42 llvm-3.1 llvm-3.2
 > > None of the specified ports are installed.
 > > }}}
 > >
 > > Which build tools is the virtualbox port supposed to use?
 >
 > My output is:
 > {{{
 > me at biboop ~> port deps virtualbox
 > Full Name: virtualbox @4.2.6_1+vde2+vnc
 > Build Dependencies:   pkgconfig, apple-gcc42
 > Library Dependencies: qt4-mac, curl, libidl, libxml2, libxslt, openssl,
 libsdl, vde2, LibVNCServer
 > me at biboop ~>
 > }}}
 >
 > Your output means you actually have an executable file at
 ''/Applications/Xcode.app/Contents/Developer/usr/bin/gcc-4.2'',
 [https://trac.macports.org/browser/trunk/dports/emulators/virtualbox/Portfile#L66
 see the Portfile].

 I don't have /Applications/Xcode.app/Contents/Developer/usr/bin/gcc-4.2. I
 do have /Applications/Xcode.app/Contents/Developer/usr/bin/gcc, though.

 {{{
 $ /Applications/Xcode.app/Contents/Developer/usr/bin/gcc-4.2
 -bash: /Applications/Xcode.app/Contents/Developer/usr/bin/gcc-4.2: No such
 file or directory
 $ /Applications/Xcode.app/Contents/Developer/usr/bin/gcc
 i686-apple-darwin11-llvm-gcc-4.2: no input files
 }}}

 It seems the virtualbox port assumes that if the configured compiler is
 available, then it's not the llvm compiler and it's safe to use. That
 assumption seems faulty. Perhaps it should just require and use the apple-
 gcc42 port unconditionally?

 > Maybe it's legacy, I'm not sure why you have that file. If you have
 still the Xcode image (i.e. the dmg not from App Store) and you want to
 get rid of it you wipe off Xcode.app and reinstall Xcode + CLI tools.

 Not sure which you mean here. Delete and install Xcode from the dmg or
 from the App Store? I like using the latter because I get updates that
 way.

 > edit:
 > this will most likely pull in apple-gcc42 and ld64, so you should get a
 working build.

 I'll try deleting and reinstalling Xcode tomorrow. Thanks for your help.

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