This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients doko, python-dev, ronaldoussoren
Date 2013-02-12.14:43:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360680210.05.0.0096655718327.issue17192@psf.upfronthosting.co.za>
In-reply-to
Content
libffi_osx is not a copy of the regular libffi, but a (fairly old) fork. I don't know how far the two "branches" have diverged.  

An important feature  of liffi_osx is that is compiles cleanly when all intel and ppc related sources are compiled with '-arch ppc -arch i386 -arch x86_64' (that is, the relevant sources contain preprocessor guards to ensure the code in those files is only compiled for the right archictures). This greatly simplifies the build process because it is not necessary to build libffi a couple of times and then merge the resulting binaries.

I'm -0 at this point w.r.t. trying to remove libffi_osx, that tree works and I'll work on it anyway (it is also used in PyObjC).
History
Date User Action Args
2013-02-12 14:43:30ronaldoussorensetrecipients: + ronaldoussoren, doko, python-dev
2013-02-12 14:43:30ronaldoussorensetmessageid: <1360680210.05.0.0096655718327.issue17192@psf.upfronthosting.co.za>
2013-02-12 14:43:30ronaldoussorenlinkissue17192 messages
2013-02-12 14:43:29ronaldoussorencreate