➜

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 blastwave
Recipients amaury.forgeotdarc, belopolsky, blastwave, meador.inge, zach.ware
Date 2016-05-27.05:29:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <9d0055e6-fc32-c1c0-9b60-db2ce1f88cbf@blastwave.org>
In-reply-to <1464300085.82.0.117497454378.issue27133@psf.upfronthosting.co.za>
Content 
On 05/26/2016 06:01 PM, Zachary Ware wrote:
>
> Zachary Ware added the comment:
>
> Would you be interested in submitting a patch?

Right now I am trying to get a clean build of libffi outside of the 
python tree and then will use the --use-system-libffi option to get 
around this mess. Of course, that sort of means that the libffi sources 
build and test clean and that, of course, is its own struggle.

see  https://sourceware.org/ml/libffi-discuss/2016/msg00024.html

and  https://sourceware.org/ml/libffi-discuss/2016/msg00025.html

I'll keep you posted on progress here.

Dennis
History
Date User Action Args
2016-05-27 05:29:00blastwavesetrecipients: + blastwave, amaury.forgeotdarc, belopolsky, meador.inge, zach.ware
2016-05-27 05:29:00blastwavelinkissue27133 messages
2016-05-27 05:29:00blastwavecreate