Fix libffi/ctypes - wrong libffi headers when building python #1609
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It has been reported of errors with
ctypes
, even when thectypes
module seems to be built fine.@tito is one of the affected by this and he found that, in some system configuration, python could be:
compiled with the headers of the system libffi, but runs with the target libffi
That will end in an app crash...
So...this pr makes that the python build make use of our libffi headers.
This would be a third solution to add to the ones proposed by @tito in #1605
This solution avoids to patch python3 and will also work for python2
!!!So many thanks @tito to found where the problem started 😄!!!