koobs added the comment: @marc I took a look at the code upstream and it does indeed appear to be the same. It was introduced in 3.1 [1].
I cant explain however how or why our Python ports work with libffi 3.2.1. See msg238767 for a link to another similar (same?) issue, with failure of OSX on 3.2.1 (building libffi, not python) [1] https://github.com/atgreen/libffi/commit/e1911f78df113ca58738b66089a070d4cf747de7 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23042> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
