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 zwelch
Recipients steve.dower, tim.golden, zach.ware, zwelch
Date 2015-01-12.22:25:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421101544.62.0.0503914606587.issue23199@psf.upfronthosting.co.za>
In-reply-to
Content
The libpython27.a is an actual 32-bit version, as confirmed by running objdump -t on it.  It reports the sections' file format as pe-i386 instead of pe-x86-64.  I am only using it for building for the 64-bit target, so I cannot confirm its viability for 32-bit builds.

To build 64-bit Windows binaries, you need a MinGW-w64 toolchain (which is a completely separate project from the original MinGW project).  The target triplet is x86_64-w64-mingw32.

I cannot speak to the stability of the MinGW-w64 library interface, but I would expect it to be stable.  To wit, I would be shocked if future changes required regeneration of third-party .a files.
History
Date User Action Args
2015-01-12 22:25:44zwelchsetrecipients: + zwelch, tim.golden, zach.ware, steve.dower
2015-01-12 22:25:44zwelchsetmessageid: <1421101544.62.0.0503914606587.issue23199@psf.upfronthosting.co.za>
2015-01-12 22:25:44zwelchlinkissue23199 messages
2015-01-12 22:25:44zwelchcreate