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 steve.dower
Recipients steve.dower, tim.golden, zach.ware, zwelch
Date 2015-01-12.21:49:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421099368.87.0.365251760181.issue23199@psf.upfronthosting.co.za>
In-reply-to
Content
Is the libpython27.a file actually a 32-bit version or is it just corrupted? It seems to be considerably smaller than the version in the 32-bit installer, but it is certainly not being generated from the 32-bit version.

I didn't write this code originally, and I don't use MinGW, so I'm not entirely familiar with how it should work. Do I need separate 64-bit tools to build the library for the 64-bit DLL or will the 32-bit tools suffice? Are the interfaces stable enough within 64-bit versions of MinGW that shipping the library makes sense, or are people likely to always need to regenerate it anyway?
History
Date User Action Args
2015-01-12 21:49:28steve.dowersetrecipients: + steve.dower, tim.golden, zach.ware, zwelch
2015-01-12 21:49:28steve.dowersetmessageid: <1421099368.87.0.365251760181.issue23199@psf.upfronthosting.co.za>
2015-01-12 21:49:28steve.dowerlinkissue23199 messages
2015-01-12 21:49:28steve.dowercreate