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 loewis
Recipients WhiteTiger, cdavid, cgohlke, cournape, eric.araujo, giampaolo.rodola, jdpipe, loewis, rubenvb, schmir, scott.tsai
Date 2012-02-05.19:42:28
SpamBayes Score 2.09557e-08
Marked as misclassified No
Message-id <>
John: in the current versions of the toolchain, Python's configure fails for me. I follow steps 1..3 of "Steps to date". Then running ./configure fails saying that it does not work. I then tried alternatively these three approaches:

1. set PATH to include /mingw/mingw/bin
2. set CC to /mingw/mingw/bin/gcc.exe
3. set CC to /c/mingw/mingw/bin/gcc.exe

Even though I can run gcc -v just fine, configure fails with

configure:3593: checking whether the C compiler works
configure:3615: /mingw/mingw/bin/gcc    conftest.c  >&5
gcc.exe: error: CreateProcess: No such file or directory^
configure:3619: $? = 1
configure:3657: result: no

So apparently, mingw has some problem mapping the file name back to a Win32 path.
Date User Action Args
2012-02-05 19:42:29loewissetrecipients: + loewis, jdpipe, giampaolo.rodola, schmir, scott.tsai, cdavid, eric.araujo, cgohlke, rubenvb, WhiteTiger, cournape
2012-02-05 19:42:29loewissetmessageid: <>
2012-02-05 19:42:29loewislinkissue4709 messages
2012-02-05 19:42:28loewiscreate