Ned Deily 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
New submission from Дилян Палаузов :
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
--
components: Build
messages: 367990
