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: compile warnings in libffi
Type: behavior Stage: resolved
Components: Build Versions: Python 3.5
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: berker.peksag, doko, steveha, zach.ware
Priority: normal Keywords:

Created on 2015-04-14 20:24 by steveha, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
libffi_warning_patch.txt steveha, 2015-04-14 20:24 patch file review
Messages (3)
msg241011 - (view) Author: Steve R. Hastings (steveha) * Date: 2015-04-14 20:24
The normal build should not have any warnings.  The source for libffi included some comparisons between signed int and unsigned int, which caused warnings.

The patch changes the signed int variables to unsigned int.
msg241024 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2015-04-14 20:50
Steve: libffi is an upstream project, so technically they should be the ones to patch it.  However, we do sometimes patch our own copy anyway and just keep the diff around.

Nosying doko as the guy who usually gets stuck handling libffi upgrades and will know better how to handle this.
msg265832 - (view) Author: Berker Peksag (berker.peksag) * (Python committer) Date: 2016-05-18 16:37
A slightly different version of the patch is now part of upstream libffi:

Thanks for the report Steve.
Date User Action Args
2022-04-11 14:58:15adminsetgithub: 68146
2016-05-18 16:37:53berker.peksagsetstatus: open -> closed

nosy: + berker.peksag
messages: + msg265832

resolution: third party
stage: resolved
2015-04-14 20:50:25zach.waresetnosy: + doko, zach.ware
messages: + msg241024
2015-04-14 20:24:08stevehacreate