[MacPorts] #30488: gavl fails to build
MacPorts
noreply at macports.org
Thu Sep 15 07:44:00 PDT 2011
#30488: gavl fails to build
-------------------------------------+--------------------------------------
Reporter: macports@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.0
Keywords: | Port: gavl
-------------------------------------+--------------------------------------
Comment(by macports@…):
Replying to [comment:6 michaelallenwarner@…]:
> P.S. I'm not sure if this makes any difference, but since the whole
32-bit vs. 64-bit thing seems to have come up in the OP by
jmr at macports.org, I thought I'd mention that my Mac's hardware (MacBook
4,1 from early 2008) is too old to run the operating system in 64 bits. So
my OS Lion runs in 32 bits (though apps can run in 64 bits).
>
The ONLY Intel Mac that can't run 64bit code is the original Core Duo
MacBook Pro. All subsequent machines are at least Core2 which can run
64bit code. The CPU should be the only thing that determines what code you
can run, and sure enough you can run plenty of 64bit apps. However, Apple
installed a 32bit build of EFI on their Macs for several years and only
switched to 64bit EFI relatively recently. That 64bit EFI is needed to run
the kernel in 64bit mode as the bootloader lacks the ability to switch
modes and launch a 64bit kernel from a 32bit environment. A little shim
can be used during the boot to fix this. Before going to that trouble
though, its worth testing what happens if you set the flag since even some
machines with a 64bit EFI (like my 2008 MacBook Pro) still boot the kernel
in 32bit mode by default. All that aside, it really doesn't matter if
kernel is in 32 or 64bit mode to anything but a kext (drivers). All apps
can execute in either regardless of which mode the kernel is in, so long
as all dependent libraries are in the correct bitness for the app. AFAIK,
macports will build x86_64 apps and libs as long as the CPU is capable,
unless your macports.conf is changed or you set +universal. So, to make
long story short, your machine isn't too old to run 64bit and most likely
your entire macports collection is being built for 64bit, including gavl.
--
Ticket URL: <https://trac.macports.org/ticket/30488#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list