From: Roumen P. <bug...@ro...> - 2013-05-23 18:13:20
|
Hi Oscar, Oscar Benjamin wrote: > On 21 May 2013 14:45, Oscar Benjamin <osc...@gm...> wrote: >> My proposal is to remove '-mno-cygwin' from distutils in Python 3.4 >> and to only use it for gcc 3.x in Python 2.7, 3.2 and 3.3. If anyone >> sees a problem with that approach I would be very grateful if you >> could let me know. Did you review my patch 0001-MINGW-issue12641-check-if-cygwin-mingw-compiler-supp.patch <http://bugs.python.org/file29032/0001-MINGW-issue12641-check-if-cygwin-mingw-compiler-supp.patch> posted to python issue issue12641 ? > Hi all, and sorry to both you again but I have one more question. > > I think I can get the above changes into distutils but there is one > last snag [1]. I can address it if I have a reliable way of querying > whether or not a given gcc is from cygwin or from mingw. I have found > a possible way to do this this by testing the output of 'gcc > -dumpmachine': > > $ /q/tools/cygwin/bin/gcc-4.exe -dumpmachine > i686-pc-cygwin > > $ /q/tools/cygwin/bin/gcc-3.exe -dumpmachine > i686-pc-cygwin > > $ /q/tools/MinGW/bin/gcc.exe -dumpmachine > mingw32 > > So I thought that I could do something like: > > if dumpmachine == "mingw32": > don't use -mno-cygwin > > or perhaps > > if dumpmachine ends with 'cygwin': > use -mno-cygwin No . Above is not enough to detect whether -mno-cygwin is supported or not. > Can anyone confirm/deny (or improve) the reliability of either of the > above methods to distinguish between cygwin and mingw gcc? > > > [1] http://bugs.python.org/issue12641#msg189770 > > > Thanks, > Oscar Roumen |