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 Jeffrey.Armstrong, Martin.Fiers, Pete.Forman, RubyTuesdayDONO, Seppo.Yli-Olli, alexis, cmcqueen1975, danmbox, doko, eric.araujo, geertj, jonforums, jwilk, loewis, oscarbenjamin, paul.moore, pje, rpetrov, rubenvb, santoso.wijaya, schmir, tarek
Date 2013-05-22.11:43:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Am 21.05.13 23:14, schrieb Oscar Benjamin:
> More generally I think that compiling non-cygwin extensions with
> cygwin gcc should be altogether deprecated (for Python 3.4 at least).
> It should be discouraged in the docs and unsupported in the future. 

I agree with that, although I find it sad that the Cygwin project
apparently abandoned support for building Mingw binaries.

> It can only work with -mno-cygwin 

This is factually incorrect. It also works with the i686-pc-mingw32-gcc
executable, which (IIUC) is still available for Cygwin.
Date User Action Args
2013-05-22 11:43:37loewissetrecipients: + loewis, doko, paul.moore, pje, geertj, schmir, tarek, jwilk, eric.araujo, rpetrov, cmcqueen1975, rubenvb, santoso.wijaya, alexis, Seppo.Yli-Olli, jonforums, RubyTuesdayDONO, Jeffrey.Armstrong, danmbox, Martin.Fiers, oscarbenjamin, Pete.Forman
2013-05-22 11:43:37loewislinkissue12641 messages
2013-05-22 11:43:37loewiscreate