Author jaharkes
Recipients bgilbert, carlkl, jaharkes, mrabarnett, paul.moore, python-dev, steve.dower, tim.golden, zach.ware
Date 2015-06-10.11:38:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433936336.24.0.892739018962.issue24385@psf.upfronthosting.co.za>
In-reply-to
Content
@Carl.Kleffner: that is an interesting message but it discusses using binutils(/mingw?) generated import libraries with the MS linker.

This bugreport was about two 64-bit objects that were accidentally included in an otherwise 32-bit library and it has been resolved.

I am not entirely sure why people are anticipating possible problems for which I have seen no actual bug reports or build failures. Searching this bugtracker for mingw related reports shows 187 reports over the past 13.5 years and at first glance I don't see any about compatibility issues between versions. There are only 3 for mingw+libpython, one of which is this report.

The various windows forks of mingw, maybe in an attempt to reach Visual C compatibility, may have as stable a format but the only failure I have personally seen was this 64-bit objects in a 32-bit library problem, which does look to me like a tool chain bug but luckily there was a relatively simple "--as-flags=--32" workaround.

I just reread my comment and I it reads ruder than I meant it to be, I'm truly sorry for that. I appreciated reading the link you included to see some of those demons lurking in the depths.
History
Date User Action Args
2015-06-10 11:38:56jaharkessetrecipients: + jaharkes, paul.moore, tim.golden, mrabarnett, python-dev, bgilbert, zach.ware, steve.dower, carlkl
2015-06-10 11:38:56jaharkessetmessageid: <1433936336.24.0.892739018962.issue24385@psf.upfronthosting.co.za>
2015-06-10 11:38:56jaharkeslinkissue24385 messages
2015-06-10 11:38:55jaharkescreate