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 paul.moore
Recipients paul.moore, steve.dower, tim.golden, zach.ware, zwelch
Date 2015-01-24.18:42:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422124936.55.0.481027167908.issue23199@psf.upfronthosting.co.za>
In-reply-to
Content
There's a lot of politics around the mingw vs mingw64 situation, but in practice I believe the various mingw64 builds are fine. So I see no reason not to supply a correct 64-bit libpythonXY.a.

When the patch was made to include the libpythonXY.a file to the msi (wow! I'd forgotten I'd ever done a patch for the MSI build) there was only 32-bit systems, and there certainly wasnt't a 64-bit mingw.

The added patch seems like a reasonable approach.
History
Date User Action Args
2015-01-24 18:42:16paul.mooresetrecipients: + paul.moore, tim.golden, zach.ware, steve.dower, zwelch
2015-01-24 18:42:16paul.mooresetmessageid: <1422124936.55.0.481027167908.issue23199@psf.upfronthosting.co.za>
2015-01-24 18:42:16paul.moorelinkissue23199 messages
2015-01-24 18:42:16paul.moorecreate