➜

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 bgilbert
Recipients bgilbert, jaharkes, mrabarnett, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-06-08.16:48:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433782093.61.0.650771511176.issue24385@psf.upfronthosting.co.za>
In-reply-to
Content 
Steve, I don't think that's the right characterization of this bug.  Putting 64-bit .o files in a 32-bit import library seems wrong for both MinGW and MinGW-w64.

msg244874 says that if you use the dlltool from the *32-bit* MinGW-w64 to build the 32-bit import library, the problem does not occur.  msg244875 says that you can even use the 64-bit MinGW-w64 dlltool by passing one additional command-line option.  Why not pursue one of those solutions?
History
Date User Action Args
2015-06-08 16:48:13bgilbertsetrecipients: + bgilbert, paul.moore, tim.golden, mrabarnett, zach.ware, steve.dower, jaharkes
2015-06-08 16:48:13bgilbertsetmessageid: <1433782093.61.0.650771511176.issue24385@psf.upfronthosting.co.za>
2015-06-08 16:48:13bgilbertlinkissue24385 messages
2015-06-08 16:48:13bgilbertcreate