On 25 May 2013 04:43, Renato Silva <report@bugs.python.org> wrote:
>
> Renato Silva added the comment:
>
> Hi Oscar! Sorry, I just meant to correct this information: "in gcc 4.x it produces an error preventing build". Even if it doesn't do anything useful, still GCC 4.4 does accept that option normally. If MinGW didn't touch anything relevant, then what Cygwin folks said about 4.x [1] clearly did not come to reality.

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?

>> No the developer does not confirm that the -mno-cygin option is
>> required for MinGW.
>
> Not for MinGW, but for building Pidgin. I have just checked it, and -mno-cygwin actually is no longer necessary since 2.10.7 [1], but it was at the time of that message. Even though it didn't do anything meaningful, a GCC like 4.6 would cause build to fail.

Yes gcc 4.6 would fail because it won't accept the -mno-cygwin option.
That does not mean that any other MinGW gcc ever *required* the
-mno-cygwin option for anything. The MinGW devs have repeatedly and
explicitly stated that the -mno-cygwin option never did anything
useful when used with MinGW:

http://permalink.gmane.org/gmane.comp.gnu.mingw.user/42097
http://permalink.gmane.org/gmane.comp.gnu.mingw.user/42101
http://permalink.gmane.org/gmane.comp.gnu.mingw.user/42104

>> 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.
>
> No, you can use either Cygwin or MinGW MSYS as environment, but the compiler must be MinGW [2].

Yes but that particular error message is coming from Cygwin's gcc not
MinGW. As stated by the Pidgin dev in that message the OP does not
know which compiler they are using:
http://pidgin.im/pipermail/support/2011-December/011159.html