Re: Compiling as 32bit on MacOSX

2010-10-14 Thread Ned Deily
In article <[email protected]>, Gregory Ewing wrote: > Ned Deily wrote: > > Perhaps you're > > calling ld(1) directly? To link multiple-arch executables (etc), the > > Apple gcc driver does the dirty work of calling ld multiple times and > > lipo-ing the results. > > Is this s

Re: Compiling as 32bit on MacOSX

2010-10-14 Thread Gregory Ewing
Ned Deily wrote: Perhaps you're calling ld(1) directly? To link multiple-arch executables (etc), the Apple gcc driver does the dirty work of calling ld multiple times and lipo-ing the results. Is this something that only works at link time, then? The gcc man page says: "Multiple options w

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Ned Deily
In article <[email protected]>, Gregory Ewing wrote: > Ned Deily wrote: > > You'll also need to specify the appropriate SDK using Apple's gcc > > -sysroot option. > Are you sure? I'm not asking for ppc + i386, I'm > asking for i386 + x86_64. I can get either of these > individuall

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Gregory Ewing
Ned Deily wrote: You'll also need to specify the appropriate SDK using Apple's gcc -sysroot option. Are you sure? I'm not asking for ppc + i386, I'm asking for i386 + x86_64. I can get either of these individually without switching SDKs. -- Greg -- http://mail.python.org/mailman/listinfo/pyth

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Philip Semanchuk
On Oct 13, 2010, at 3:54 AM, Gregory Ewing wrote: > Philip Semanchuk wrote: > >> Hi Greg, >> Are you talking about compiling Python itself or extensions? > > I've managed to get Python itself compiled as 32 bit, > and that also seems to take care of extensions built > using 'python setup.py ...

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Ned Deily
In article <[email protected]>, Gregory Ewing wrote: > On a related note, according to the man page for Apple's > gcc, you're supposed to be able to use both '-arch i386' > and '-arch x86_64' at the same time and get fat binaries. > That would actually be my preferred option, becaus

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Diez B. Roggisch
Gregory Ewing writes: > Philip Semanchuk wrote: > >> Hi Greg, >> Are you talking about compiling Python itself or extensions? > > I've managed to get Python itself compiled as 32 bit, > and that also seems to take care of extensions built > using 'python setup.py ...'. > > I'm mainly concerned ab

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Gregory Ewing
Jason Swails wrote: Try setting the compiler itself as "gcc -m32" You mean by setting CC? That's a cunning plan -- I'll give it a try. On a related note, according to the man page for Apple's gcc, you're supposed to be able to use both '-arch i386' and '-arch x86_64' at the same time and get f

Re: Compiling as 32bit on MacOSX

2010-10-13 Thread Gregory Ewing
Philip Semanchuk wrote: Hi Greg, Are you talking about compiling Python itself or extensions? I've managed to get Python itself compiled as 32 bit, and that also seems to take care of extensions built using 'python setup.py ...'. I'm mainly concerned about non-Python libraries that get wrappe

Re: Compiling as 32bit on MacOSX

2010-10-12 Thread Philip Semanchuk
On Oct 12, 2010, at 8:29 PM, Gregory Ewing wrote: > I'm getting my Python environment set up on a new > Snow Leopard machine, and I'd like to compile everything > in 32 bit mode for the time being, because some of the > extensions I need use APIs that aren't available in > 64 bit. > > Is there s

Re: Compiling as 32bit on MacOSX

2010-10-12 Thread Ned Deily
In article <[email protected]>, Gregory Ewing wrote: > I'm getting my Python environment set up on a new > Snow Leopard machine, and I'd like to compile everything > in 32 bit mode for the time being, because some of the > extensions I need use APIs that aren't available in > 64 bit

Re: Compiling as 32bit on MacOSX

2010-10-12 Thread MRAB
On 13/10/2010 01:29, Gregory Ewing wrote: I'm getting my Python environment set up on a new Snow Leopard machine, and I'd like to compile everything in 32 bit mode for the time being, because some of the extensions I need use APIs that aren't available in 64 bit. Is there some environment variab

Re: Compiling as 32bit on MacOSX

2010-10-12 Thread Jason Swails
Try setting the compiler itself as "gcc -m32" -- Jason Swails Quantum Theory Project, University of Florida Ph.D. Graduate Student 352-392-4032 On Oct 12, 2010, at 8:29 PM, Gregory Ewing wrote: > I'm getting my Python environment set up on a new > Snow Leopard machine, and I'd like to compile e

Compiling as 32bit on MacOSX

2010-10-12 Thread Gregory Ewing
I'm getting my Python environment set up on a new Snow Leopard machine, and I'd like to compile everything in 32 bit mode for the time being, because some of the extensions I need use APIs that aren't available in 64 bit. Is there some environment variable or config setting that will make gcc com