➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2020-05-03 19:54 by dilyan.palauzov, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg367990 - (view) | Author: Дилян Палаузов (dilyan.palauzov) | Date: 2020-05-03 19:54 | |
With libffi 3.3 doing `./configure && make install` puts libffi.so in /usr/local/lib64/ . This can be found by pkgconfig. But setup.py neither uses pkgconfig, nor checks by default /usr/local/lib64 for libffi |
|||
| msg368417 - (view) | Author: Ned Deily (ned.deily) *  |
Date: 2020-05-08 03:27 | |
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. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:30 | admin | set | github: 84668 |
| 2020-05-08 03:27:34 | ned.deily | set | status: open -> closed superseder: How to link with a non-system libffi? nosy: + ned.deily messages: + msg368417 resolution: duplicate stage: resolved |
| 2020-05-03 19:54:08 | dilyan.palauzov | create | |