Ronald Oussoren added the comment: I don't know how the main copy of libffi in the CPython tree is updated, and if it is a straight copy of the upstream release. Given the mercurial log I'd guess that Modules/_ctypes/libffi is libffi 3.0.11 with a small patch in Modules/_ctypes/libffi.diff.
As Arfrever notes libffi_osx is used on OSX only, and that version is a fork of libffi shared with PyObjC (that is, I try to update the copy in the CPython tree whenever I have to update the copy for PyObjC). I agree that the issue with libffi should be fixed upstream first, otherwise it would get harder and harder to import new upstream versions. ---------- nosy: +doko _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17136> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
