Gregory Ewing <greg.ew...@canterbury.ac.nz> 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 about non-Python libraries that > get wrapped by the extensions, of which I've built up > quite a collection over the years. Currently I'm having > to keep a careful eye out when building them to make > sure they don't get compiled with the wrong architecture, > since gcc's natural inclination is to default to 64 bit > whenever it's available. > > So I was wondering if there was some way of globally > changing that default that doesn't rely on compiler > options getting passed correctly through the many and > varied layers of build technology that one comes across. > But from what I've seen so far, it seems not.
If all you have is a fat-binary, you can still work with that using the lipo-tool to remove those architectures you are not interested in. Diez -- http://mail.python.org/mailman/listinfo/python-list
