koobs added the comment: @Marc, if upstream 3.2.1 also has the issue, then that would mean the current FreeBSD Python ports, which use --use-system-ffi and the security/libffi port, currently at version 3.2.1 [1], can reproduce the issue.
I'm not aware of reports that they fail in this manner though. [1] http://www.freshports.org/devel/libffi/ ---------- title: ctypes module doesn't build on FreeBSD x86 -> ctypes module doesn't build on FreeBSD, RHEL (x86) - Undefined symbol "ffi_call_win32" _______________________________________ 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
