Re: [Chicken-users] OS X 10.6 (Snow Leopard)

[Jim Ursetto]

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 perfectly fine on OS X, except that you must remember to
build all your local libraries in 64-bit mode.  If 64-bit is now the
standard output format, then this is not an issue and we should prefer
64-bit when available.  I do not have a copy of 10.6 to play around
with yet though.

On Sat, Aug 29, 2009 at 9:56 PM, Jim Ursetto<address@hidden> wrote:
> 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 Piper<address@hidden> 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 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 native 64-bit Chicken, you need to make sure apply-hack.x86-64.s is
>> built.  I just edited config-arch.sh and changed the 'x86' to 'x86-64':
>>
>> 30c30
>> <     i*86) echo "x86";;
>> ---
>>>     i*86) echo "x86-64";;
>>
>> fluffy% csi
>>
>> CHICKEN
>> (c)2008 The Chicken Team
>> (c)2000-2007 Felix L. Winkelmann
>> Version 3.4.0 - macosx-unix-gnu-x86-64  [ 64bit manyargs dload ptables
>> applyhook ]
>> compiled 2009-08-29 on fluffy.local (Darwin)
>>
>>
>>
>> _______________________________________________
>> Chicken-users mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/chicken-users
>>
>