Ned Deily <n...@python.org> added the comment:
Thanks for the report and for the analysis. There have been a number of reports over the years about problems trying to build and/or execute Pythons with an external copy of libffi. They have become more pressing now that we no longer vendor the source of libffi in Python source releases. To help focus on the issues, we are consolidating the discussion in Issue14527, one of the earliest opened issues. ---------- nosy: +ned.deily -FFY00 resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> How to link with a non-system libffi? _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40535> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
