[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

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

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Paul Hege added the comment: I had also received the same warnings when running make: "INFO: Could not locate ffi libs and/or headers" and "Failed to build these modules: _ctypes". Although Python could still be installed, the pip command was not installed, and installing it using get_pip.py

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Change by Chih-Hsuan Yen : -- nosy: -yan12125 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Ivan Levchenko added the comment: Was having the same issue compiling python 3.7.1 against locally compilied libffi 3.2.1. Setting CPPFLAGS and LDFLAGS was not enough and was still getting the same error: INFO: Could not locate ffi libs and/or headers Everything worked as soon as i added

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Matt Pruitt added the comment: Also ran into this issue while building Python in an isolated environment. Realized that libffi is installing into the $EPREFIX/lib64 directory of our build environment. Despite pkg-config returning the correct directory for linking libffi, it took

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Chih-Hsuan Yen added the comment: Thanks for providing the info. However, I'm sorry as the case is beyond my knowledge. Here's the relevant section in CPython that handles LIBFFI path searching: https://github.com/python/cpython/blob/v3.7.0/setup.py#L1984-L2002. You may want to examine

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Roy Belio added the comment: as seen in the config.log: LIBFFI_INCLUDEDIR='/root/rc3/dist/lib/libffi-3.2.1/include' I'm attaching the config.log just in case -- Added file: https://bugs.python.org/file47729/config.log ___ Python tracker

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Chih-Hsuan Yen added the comment: A possible case might be that pkg-config on your build machine is not properly configured. Could you check the value of LIBFFI_INCLUDEDIR in config.log? It shuold either be an empty string or /root/rc3/dist/lib/libffi-3.2.1/include. As a reference, the

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Roy Belio added the comment: Sure, I'll attach it. one more thing to mention is that during configure it printed: configure: WARNING: --with(out)-system-ffi is ignored on this platform We are also providing all the dependency libraries ourselves (building, linking, h files and what not) so

[issue31710] setup.py: _ctypes won't get built when system ffi is only in $PREFIX

Change by ppperry : -- title: setup.py: _ctypes won't getbuilt when system ffi is only in $PREFIX -> setup.py: _ctypes won't get built when system ffi is only in $PREFIX ___ Python tracker