[issue44556] ctypes unittest crashes with libffi 3.4.2

Ned Deily added the comment: Yes, this does appear to be a result of the problem described in Issue45350. As noted there, the problem was caused by running autoreconf to regerenerate the ./configure script in an environment where pkg-config wasn't installed which caused some pkg-config code

[issue44556] ctypes unittest crashes with libffi 3.4.2

Isuru Fernando added the comment: Duplicate of https://bugs.python.org/issue45350 -- nosy: +isuruf ___ Python tracker ___ ___

[issue44556] ctypes unittest crashes with libffi 3.4.2

Eli Rykoff added the comment: To add a bit more color, I don't think you can explicitly set LIBFFI_INCLUDE_DIR, it's set by the configure script explicitly. The problem is that some time between python 3.9 and 3.10 the configure script has (at least in our system) failed to figure out the

[issue44556] ctypes unittest crashes with libffi 3.4.2

jakirkham added the comment: We ran into the same issue in conda-forge ( https://github.com/conda-forge/python-feedstock/issues/522 ). The problem is Apple also supplies their own `libffi`. However if the build scripts in CPython fail to find the user provided `libffi`, they end up pulling

[issue44556] ctypes unittest crashes with libffi 3.4.2

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44556] ctypes unittest crashes with libffi 3.4.2

Change by Ryan May : -- nosy: +Ryan May ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44556] ctypes unittest crashes with libffi 3.4.2

New submission from Zan : Running the unittests after upgrading libffi to latest version 3.4.2 and recompiling python, leads to several tests in Lib/ctypes/test/ to crash with Abort: trap 6. This does not happen with version 3.3 of libffi. Steps to reproduce: git clone