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-20.22:20:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421792422.88.0.38713799981.issue23199@psf.upfronthosting.co.za>
In-reply-to
Content
Just came across this advice on https://github.com/cython/cython/wiki/64BitCythonExtensionsOnWindows:

> Do not use MinGW-w64. As you will notice, the MinGW import library for
> Python (e.g. libpython27.a) is omitted from the AMD64 version of
> Python. This is deliberate. Do not try to make one using dlltool.
> There is no official MinGW-w64 release yet, it is still in "beta" and
> considered unstable, although you can get a 64-bit build from e.g.
> TDM-GCC. There have also been issues with the mingw runtime
> conflicting with the MSVC runtime; this can happen from places you
> don't expect, such as inside runtime libraries for g++ or gfortran. To
> stay on the safe side, avoid MinGW-w64 for now.

How accurate is this? Would we be better to omit the mingw libraries from the installer and instead provide the commands (or even a shell script?) to generate it with whatever toolset you're currently using?
History
Date User Action Args
2015-01-20 22:20:22steve.dowersetrecipients: + steve.dower, tim.golden, zach.ware, zwelch
2015-01-20 22:20:22steve.dowersetmessageid: <1421792422.88.0.38713799981.issue23199@psf.upfronthosting.co.za>
2015-01-20 22:20:22steve.dowerlinkissue23199 messages
2015-01-20 22:20:22steve.dowercreate