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 erik.bray
Recipients dellair.jie, erik.bray, loewis, masamoto, r.david.murray, rpetrov, vstinner
Date 2016-08-30.10:09:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472551743.32.0.896488334491.issue21085@psf.upfronthosting.co.za>
In-reply-to
Content
I've reviewed masamoto's last patch 3.5-issue21085-struct_siginfo-2.patch

It applies cleanly and allows the signals module to compile on Cygwin64 2.5.1 / Windows 10.  I attached versions of the patch that apply cleanly to tip, 3.4, and 3.3 as well.

However, even with this issue resolved it can't be fully tested because there are other open issues preventing a successful build on Cygwin, including issue25658 and issue13756

Would it be ok to commit this even though it doesn't resolve all build issues?  Or should I try to cobble together a meta-issue of current known build issues and make sure they all have working patches first?
History
Date User Action Args
2016-08-30 10:09:03erik.braysetrecipients: + erik.bray, loewis, vstinner, rpetrov, r.david.murray, dellair.jie, masamoto
2016-08-30 10:09:03erik.braysetmessageid: <1472551743.32.0.896488334491.issue21085@psf.upfronthosting.co.za>
2016-08-30 10:09:03erik.braylinkissue21085 messages
2016-08-30 10:09:03erik.braycreate