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 oscarbenjamin
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, renatosilva, rpetrov, rubenvb, santoso.wijaya, schmir, tarek
Date 2013-05-24.10:52:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Renato Silva added the comment:
> I must note that GCC 4.x *does* support -mno-cygwin, at least until 4.4,
and at least the MinGW version.

MinGW has never "supported" the -mno-cygwin option. It has simply tolerated
it. The option never did anything useful and at some point it became an
error to even supply it. I'm not sure exactly when but some time after 4.4
sounds reasonable to me.

The option was only ever meaningful in cygwin's gcc 3.x and was always an
error in 4.x.

> I have used it myself for building Pidgin under Windows, which requires
that option. See [1] where a Pidgin developer confirms that.

No the developer does not confirm that the -mno-cygin option is required
for MinGW. Also from what I've seen I would say that the error message that
the OP shows there comes from Cygwin's gcc not MinGW.
Date User Action Args
2013-05-24 10:52:19oscarbenjaminsetrecipients: + oscarbenjamin, 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, Pete.Forman, renatosilva
2013-05-24 10:52:19oscarbenjaminlinkissue12641 messages
2013-05-24 10:52:19oscarbenjamincreate