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
Daniel Fetchinson added the comment:
It seems there is a way to fix this:
https://mail.python.org/pipermail/python-list/2018-December/738568.html
LDFLAGS=`pkg-config --libs-only-L libffi` ./configure
Would be nice to document this or make the build system find the libraries and
headers in
Daniel Fetchinson added the comment:
I have the exact same issue, trying to compile 3.7.1 with a custom libffi
location. Note that I must build libffi from source and can't install binaries
provided by my distro, I believe this is the origin of the problem. Probably
the python build system
Daniel Fetchinson added the comment:
It would be really great if this could be sorted out because at the moment this
bug prevents me from using numpy/scipy with python 3.7.1 (they need _ctypes).
--
__
Python tracker
New submission from Michael Stapelberg :
(Tested with Python 3.7, but AFAICT, the situation hasn’t changed in Python
3.8.)
Python’s configure tries to fill the LIBFFI_INCLUDEDIR system variable with the
value of -I as returned by pkg-config libffi --cflags-only-I.
Python’s setup.py tries to
