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 jdpipe
Recipients WhiteTiger, cdavid, cgohlke, cournape, eric.araujo, giampaolo.rodola, jdpipe, loewis, rubenvb, schmir, scott.tsai
Date 2012-02-06.16:25:03
SpamBayes Score 2.08563e-08
Marked as misclassified No
Message-id <1328545504.04.0.435359911963.issue4709@psf.upfronthosting.co.za>
In-reply-to
Content
Martin, Ralf is right and my as previously linked is about building a python extension. I should have been more explicit about that.

FWIW I found that the configure scripts on MinGW-w64 generally work fine if you add a "--build=x86_64-w64-mingw32" argument on the ./configure command line. Then you should only add /mingw/bin to your path (and edit /etc/fstab to map c:/mingw64 to /mingw). Adding those subdirectories to the PATH doesn't seem to be successful; I suspect that those binaries are off the standard path for some reason, eg internal use by GCC only, or something (GCC seems to do some clever tricks with relative paths, so I'm sure it's important that you use the correct starting executable).
History
Date User Action Args
2012-02-06 16:25:04jdpipesetrecipients: + jdpipe, loewis, giampaolo.rodola, schmir, scott.tsai, cdavid, eric.araujo, cgohlke, rubenvb, WhiteTiger, cournape
2012-02-06 16:25:04jdpipesetmessageid: <1328545504.04.0.435359911963.issue4709@psf.upfronthosting.co.za>
2012-02-06 16:25:03jdpipelinkissue4709 messages
2012-02-06 16:25:03jdpipecreate