[issue14527] How to link with a non-system libffi?

Change by Sam James : -- nosy: +thesamesam ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue14527] How to link with a non-system libffi?

Change by Christian Heimes : -- type: -> enhancement versions: +Python 3.10, Python 3.11 ___ Python tracker ___ ___ Python-bugs-lis

[issue14527] How to link with a non-system libffi?

Rupert Nash added the comment: Due to some major changes in setup.py around libffi, I've had to re-implement my patch - please see Github. I'd appreciate any comments so we can get this merged. Thanks! -- ___ Python tracker

[issue14527] How to link with a non-system libffi?

pmp-p added the comment: I think the actual PR20451 with its proper use of pkgconfig could close https://bugs.python.org/issue31710 ( fixing at once android and wasm/wasi compilation ) -- ___ Python tracker __

[issue14527] How to link with a non-system libffi?

Raphael Krut-Landau added the comment: To install Python 3.9 locally, with ctypes, this worked for me. # I created a temp directory cd ~ mkdir tmp cd tmp # I downloaded and installed the latest libffi source from Github wget "https://github.com/libffi/libffi/releases/download/v3.3/libffi-3.3.

[issue14527] How to link with a non-system libffi?

Change by pmp-p : -- nosy: +pmpp ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mail

[issue14527] How to link with a non-system libffi?

Change by pmp-p : -- nosy: -pmpp ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

[issue14527] How to link with a non-system libffi?

Change by pmp-p : -- nosy: +pmpp ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mail

[issue14527] How to link with a non-system libffi?

wang zhao added the comment: We managed to fixed on the server by following and got it sucuessfully compiled: -./configure --with-system-ffi LDFLAGS="-L /home/XXX/installs/libffi-3.3/lib64/" CPPFLAGS="-I /home/XXX/installs/libffi-3.3/include/" -LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/XXX/ins

[issue14527] How to link with a non-system libffi?

Change by Joshua Merchant : -- nosy: +Joshua Merchant ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue14527] How to link with a non-system libffi?

Warren Hardy added the comment: I tried Rupert Nash’s changes to Makefile.pre.in, configure, configure.ac and setup.py. I can confirm this changes worked for me. I had to edit the Makefile and enter the LIBFFI_INCLUDEDIR and LIBFFI_LIBDIR this might be due to me being a newb about this stuf

[issue14527] How to link with a non-system libffi?

Rupert Nash added the comment: I have just struggled with building CPython with the _ctypes module. Fundamentally, the problem appears to be that configure uses pkgconfig to find the libffi include directory, while setup.py's detect_ctypes only uses the global list of library directories. I

[issue14527] How to link with a non-system libffi?

Change by Rupert Nash : -- keywords: +patch nosy: +rnash nosy_count: 3.0 -> 4.0 pull_requests: +19705 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/20451 ___ Python tracker

[issue14527] How to link with a non-system libffi?

Ned Deily added the comment: See also earlier discussions in Issue31710, Issue34823, Issue40488, and Issue40535, closed as duplicated of this issue. -- stage: -> needs patch type: enhancement -> ___ Python tracker

[issue14527] How to link with a non-system libffi?

Ned Deily added the comment: As of current Python 3 releases, like 3.8, the python build no longer vendors a copy of libffi for most Unix systems and for those systems the --with-system-ffi configure option is ignored, i.e. configure and setup.py will always try to find an external libffi.