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.

Title: ctypes (libffi) fails to compile on Solaris X86
Type: compile error Stage: resolved
Components: ctypes Versions: Python 3.6, Python 3.4, Python 3.5, Python 2.7
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: CristiFati, amaury.forgeotdarc, belopolsky, doko, meador.inge, ned.deily
Priority: normal Keywords: patch

Created on 2015-10-15 14:33 by CristiFati, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
Python-2.7.10-ux_x86_libffi.patch CristiFati, 2015-10-15 14:33
Messages (4)
msg253048 - (view) Author: Cristi Fati (CristiFati) * Date: 2015-10-15 14:33
2.7.10 regression (at least compared to 2.7.3), not sure which exact version between the 2 first introduced it.

Due to addition of `win32.S` in the list build on Solaris X86 (32bit which also identifies the platform as X86) fails.

Attaching a patch. After applying it, compiles and runs on Solaris X86 and Windowses.
msg268131 - (view) Author: Matthias Klose (doko) * (Python committer) Date: 2016-06-10 17:42
CristiFati, please could you check if the libffi patch is still needed with the current upstream libffi?

msg268427 - (view) Author: Cristi Fati (CristiFati) * Date: 2016-06-13 07:31
Hi, sorry for spamming everyone, I couldn't find a way to reply to the
last message directly on #25413 (

Looked over the current version (from MASTER) of the file:, and it
significantly differs from the one distributed in Python 2.7.10 (and
2.7.11). For example, all the conditional macros (out of which most
are Windows related) are gone. So, the patch is not (even close)
compatible with the current libffi version.

On Fri, Jun 10, 2016 at 8:42 PM, Matthias Klose <> wrote:
> Matthias Klose added the comment:
> CristiFati, please could you check if the libffi patch is still needed with the current upstream libffi?
> See
> ----------
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
msg368409 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2020-05-08 02:47
As of Python 3.7, we no longer "vendor" a copy of the libffi source in Python source releases; you either need to use a system-supplied libffi, a third-party binary, or build it youself.  Also Python 2.7 has reached end-of-life and is now frozen.  So, if any libffi compile problems remain, they would need to be pursued with the libffi project.
Date User Action Args
2022-04-11 14:58:22adminsetgithub: 69599
2020-05-08 02:47:09ned.deilysetstatus: open -> closed

nosy: + ned.deily
messages: + msg368409

resolution: out of date
stage: resolved
2016-06-13 07:31:33CristiFatisetmessages: + msg268427
2016-06-10 17:42:43dokosetmessages: + msg268131
2016-05-22 11:35:51berker.peksagsetnosy: + doko
2015-10-20 22:10:04pitrousetnosy: + amaury.forgeotdarc, belopolsky, meador.inge

versions: + Python 3.4, Python 3.5, Python 3.6
2015-10-15 14:33:45CristiFaticreate