This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients ned.deily, tturbs
Date 2020-05-08.02:35:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1588905340.47.0.0415521401152.issue35061@roundup.psfhosted.org>
In-reply-to
Content
Sorry for the long delay in answering this issue: ctypes and libffi issues do not get a lot of attention currently. I assume you must have long ago found a solution to the problem but, just for the record and assuming I understand the problem correctly, if you build Python on centos6 with its default libffi.so.5 and then try to move those binaries to a centos7 system that does not include a libffi.so.5 along with libffi.so.6, you are out of luck.  Normally, the change from .5 to .6 would indicate some ABI incompatibility between the two libffi versions. Rebuilding Python on centos7 should produce a working Python that links with the latest library versions, including libffi, available on that centos release.
History
Date User Action Args
2020-05-08 02:35:40ned.deilysetrecipients: + ned.deily, tturbs
2020-05-08 02:35:40ned.deilysetmessageid: <1588905340.47.0.0415521401152.issue35061@roundup.psfhosted.org>
2020-05-08 02:35:40ned.deilylinkissue35061 messages
2020-05-08 02:35:39ned.deilycreate