Renato Silva added the comment:
> In context it should be clear that the statement "in gcc 4.x it
> produces an error preventing build" refers to Cygwin's gcc and not
> MinGW's. Which gcc are you referring to?
If it refers to Cygwin only, sorry then. However, didn&
Changes by Renato Silva :
--
nosy: -renatosilva
___
Python tracker
<http://bugs.python.org/issue12641>
___
___
Python-bugs-list mailing list
Unsubscribe:
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. I have used it myself for building Pidgin under
Windows, which requires that option. See [1] where a Pidgin developer confirms
that.
[1] http://pidgin.im
Renato Silva added the comment:
> 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 s
Renato Silva added the comment:
ERRATA.
Where you see: "[1] clearly did not come to reality."
Please read: "[0] clearly did not come to reality."
[0] http://cygwin.com/ml/cygwin/2009-03/msg00802.html
--
___
Python tracker
<
