Author ronaldoussoren
Recipients matrixise, ned.deily, r.david.murray, ronaldoussoren, yan12125, zach.ware
Date 2016-10-21.11:25:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477049121.06.0.949040962854.issue28491@psf.upfronthosting.co.za>
In-reply-to
Content
Does the upstream libffi work reliably on OSX by this time?  

The bundled version of libffi was extracted from PyObjC, and that copy is itself a patched version of the system libffi on OSX. The reason I don't use the system libffi is both that I don't want to rely on older version of libffi, and because the system libffi causes crashes in PyObjC's testsuite (which contains a lot of edge cases). 

I haven't looked into using the upstream version of libffi yet. PyObjC's version of libffi is a fairly old fork of upstream libffi where support for other systems was removed and support for darwin/x86 (and later darwin/x86-64) as added. The former at a time that the upstream libffi didn't support darwin/x86 at all (and at a time that darwin/x86 itself wasn't available on consumer devices).
History
Date User Action Args
2016-10-21 11:25:21ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, r.david.murray, zach.ware, matrixise, yan12125
2016-10-21 11:25:21ronaldoussorensetmessageid: <1477049121.06.0.949040962854.issue28491@psf.upfronthosting.co.za>
2016-10-21 11:25:21ronaldoussorenlinkissue28491 messages
2016-10-21 11:25:20ronaldoussorencreate