[issue23958] compile warnings in libffi

[Berker Peksag]

Berker Peksag added the comment:

A slightly different version of the patch is now part of upstream libffi: 
https://github.com/libffi/libffi/commit/4a677a425c18eda4bc5357b2485da57f133f908d

Thanks for the report Steve.

--
nosy: +berker.peksag
resolution:  -> third party
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23958] compile warnings in libffi

[Steve R. Hastings]

New submission from Steve R. Hastings:

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.

--
components: Build
files: libffi_warning_patch.txt
messages: 241011
nosy: steveha
priority: normal
severity: normal
status: open
title: compile warnings in libffi
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file39017/libffi_warning_patch.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23958
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23958] compile warnings in libffi

[Zachary Ware]

Zachary Ware added the comment:

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.

--
nosy: +doko, zach.ware

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23958
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com