Yes, building with ARCH=x86-64 works.
On Aug 29, 2009, at 10:32 PM, Jim Ursetto wrote:
OK, we will have to deal with this then. In the meantime, can you
confirm that building with ARCH=x86-64 fixes the problem as well?
On Sat, Aug 29, 2009 at 11:05 PM, Derrell Piperd...@electric-
loft.org
It appears that the native Xcode 3.2 build tools are now 64-bit on
10.6 and config-arch.sh isn't smart enough to distinguish the 64-
bitness. As a result, it assembles the 32-bit apply-hack and then
fails to construct libchicken.a because there's a mix of 32-bit and 64-
bit .o's.
To get a
It might be easier to compile with
make PLATFORM=macosx ARCH=x86-64
as stated in the README.
Jim
On Sat, Aug 29, 2009 at 7:35 PM, Derrell Piperd...@electric-loft.org wrote:
It appears that the native Xcode 3.2 build tools are now 64-bit on 10.6 and
config-arch.sh isn't smart enough to
Is it really true that 10.6 gcc defaults to producing 64-bit binaries?
I imagine that would break a lot of traditional UNIX builds. If so
then we will need to either have better detection of bittedness or
simply force gcc to 32-bit mode unless the ARCH is specified as
64-bit.
64-bit works
OK, we will have to deal with this then. In the meantime, can you
confirm that building with ARCH=x86-64 fixes the problem as well?
On Sat, Aug 29, 2009 at 11:05 PM, Derrell Piperd...@electric-loft.org wrote:
I was pretty surprised myself. But it seems that's the path they chose:
fluffy% gcc
