Why does Virtualbox need Universal binaries?

John Ruschmeyer jruschme at gmail.com
Thu May 16 03:50:10 PDT 2013


Second on the "buildbot + universal" suggestion.

That was my big disappointment with building Virtualbox- now almost every
package has going to have to be built from source, rather than installed
from binary from now on.


On Wed, May 15, 2013 at 7:32 PM, Bradley Giesbrecht <pixilla at macports.org>wrote:

> On May 15, 2013, at 1:40 PM, Ryan Schmidt wrote:
>
> >
> > On May 15, 2013, at 15:38, John Ruschmeyer wrote:
> >
> >> I decided to install Virtualbox via MacPorts as opposed to installing
> the binary from Oracle. What has happended, though, is that MacPorts has
> started recompiling dependencies with "+Universal" (currently on glib2).
> >>
> >> What I don't understand is why this is necessary, particularly since
> Virtualbox will never run on anything other than an Intel-based system?
> >
> > Virtualbox installs a kernel extension. So it needs to build for the
> same architecture as your kernel.
> >
> > Your Mac is presumably one of the early Intel Macs that uses a 32-bit
> kernel, therefore Virtualbox builds itself 32-bit. In order to do that,
> MacPorts must first rebuild all of its dependencies universal (32-bit and
> 64-bit).
>
> buildbot +universal would be nice
>
>
> Regards,
> Bradley Giesbrecht (pixilla)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130516/ab0c8dbc/attachment.html>


More information about the macports-users mailing list