|
From: Greg C. <gch...@sb...> - 2013-05-20 15:58:48
|
On 2013-05-20 14:54Z, Paul Moore wrote: [...] > The OP is trying to gather evidence that it is *not possible* for people to > be relying on the existing broken behaviour, because it cannot produce > viable executables (the only versions of gcc that could exist anywhere > which accept -mno-cygwin, do not support building with the version of > MSVCRT that Python needs). If he can *prove* that there are no users who > will be adversely impacted by the change, it might be possible to get the > change moving at last. http://cygwin.com/ml/cygwin/2009-03/msg00802.html | gcc-3 -mno-cygwin still works just as well (or badly!) as it ever has done, | and will be retained for ever. Some people may still be using Cygwin gcc version 3, which needs '-mno-cygwin'. Those are the only people who might be affected. |