[issue12641] Remove -mno-cygwin from distutils
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't folks said in MinGW thread that they didn't touch anything about such flag there? If so, then how can it have been removed later in 4.5 or 4.6 instead of 4.0 like in Cygwin? > 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. Again, I was not saying it was required *for MinGW*, but *for building Pidgin*. Note that I'm not saying either that their use of such option was ever meaningful in the build process (in fact, they have removed such flag while still using 4.4, indicating that it was really useless). > 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 We actually cannot confirm whether the GCC was from Cygwin, MSYS or Pidgin build box (the correct), and which version. It could be from Cygwin, but still my point stands, that the Pidgin developer does confirm that GCC 4.4 from MinGW *does* accept that flag. -- ___ Python tracker <http://bugs.python.org/issue12641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12641] Remove -mno-cygwin from distutils
Changes by Renato Silva : -- nosy: -renatosilva ___ Python tracker <http://bugs.python.org/issue12641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12641] Remove -mno-cygwin from distutils
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/pipermail/support/2011-December/011159.html -- nosy: +renatosilva ___ Python tracker <http://bugs.python.org/issue12641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12641] Remove -mno-cygwin from distutils
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 sounds reasonable to me. 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. > 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. > 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]. [1] https://hg.pidgin.im/pidgin/main/rev/c959cde2a7bd [2] https://developer.pidgin.im/wiki/BuildingWinPidgin#Setupyourbuildenvironment -- ___ Python tracker <http://bugs.python.org/issue12641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12641] Remove -mno-cygwin from distutils
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 <http://bugs.python.org/issue12641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
