➜

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 vmurashev
Recipients paul.moore, steve.dower, tim.golden, vmurashev, zach.ware
Date 2016-09-25.09:45:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474796748.74.0.791284991149.issue28267@psf.upfronthosting.co.za>
In-reply-to
Content 
Hi,here the issue:
We (crystax.net) use custom builds of cpython,
which for windows are compiled by MinGW with pyconfig.h taken from PC/pyconfig.h
And for 32-bit Windows everything works well, but for 64-bit Windows - doesn't.

The root cause of this issue is actauly very simple:

Python code for windows is very sensitive on properly defined macro MS_WIN32/MS_WIN64
And while MS_WIN32 is predefined unconditionally in PC/pyconfig.h,
the MS_WIN64 is defined only in conjunction with _MSC_VER, like

#ifdef _MSC_VER
...
#ifdef _WIN64
#define MS_WIN64
#endif
...
#endif /* _MSC_VER */

So suggested patch (for 3.5.2 and 2.7.12) just appropriately define MS_WIN64 for MinGW
History
Date User Action Args
2016-09-25 09:45:48vmurashevsetrecipients: + vmurashev, paul.moore, tim.golden, zach.ware, steve.dower
2016-09-25 09:45:48vmurashevsetmessageid: <1474796748.74.0.791284991149.issue28267@psf.upfronthosting.co.za>
2016-09-25 09:45:48vmurashevlinkissue28267 messages
2016-09-25 09:45:48vmurashevcreate