➜

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 lemburg
Recipients Arfrever, doko, fabiovmp, gustavotemple, koobs, lemburg, meador.inge, steve.dower, tim.golden, zach.ware
Date 2015-05-15.09:25:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431681956.55.0.961544677152.issue23085@psf.upfronthosting.co.za>
In-reply-to
Content 
issue23042 is fixed now. libffi 3.2.1 apparently has the same issue, so the issue23042 patch would probably have to be reapplied (slightly modified, though).

Seeing that libffi has had a major compilation problem breaking it on at least FreeBSD and most probably a lot of other x86 based systems as well, I don't really have much confidence in the libffi maintenance, so the usual "latest is the greatest" may not be the best approach.

Are there any issue *we* have with libffi which an update to 3.2.1 would solve ?
History
Date User Action Args
2015-05-15 09:25:56lemburgsetrecipients: + lemburg, doko, tim.golden, Arfrever, meador.inge, zach.ware, koobs, steve.dower, gustavotemple, fabiovmp
2015-05-15 09:25:56lemburgsetmessageid: <1431681956.55.0.961544677152.issue23085@psf.upfronthosting.co.za>
2015-05-15 09:25:56lemburglinkissue23085 messages
2015-05-15 09:25:56lemburgcreate