Message 191845 - Python tracker

Message191845

Author	oscarbenjamin
Recipients	Jeffrey.Armstrong, Martin.Fiers, Pete.Forman, RubyTuesdayDONO, Seppo.Yli-Olli, alexis, cmcqueen1975, danmbox, doko, eric.araujo, fratti, geertj, jonforums, jwilk, lemburg, loewis, oscarbenjamin, paul.moore, pje, renatosilva, rpetrov, rubenvb, santoso.wijaya, schmir, tarek
Date	2013-06-25.10:47:06
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAHVvXxQMyRUCQCEF+-hk_qpxEpN3SBLA15NAWYqnny925N=EuQ@mail.gmail.com>
In-reply-to	<CAHVvXxTFXnyRekdf_8iowpqH8L1Jd1j1zkDTGK36Y_E+Jkjj3g@mail.gmail.com>

Content
I'm attaching one more patch "check_mno_cywin_py34.patch". This is my preferred patch for Python 3.4 (default). It fixes building with MinGW and removes all support for using Cygwin gcc with --compiler=mingw32. The user would see the following error message: ''' Q:\current\testing\hello>testbuild q:\tools\cygwin\bin -3.3 running build_ext error: Cygwin gcc cannot be used with --compiler=mingw32 ''' I think that this is reasonable as '-mno-cygwin' is a previously experimental and now long deprecated, discouraged and discontinued feature of Cygwin's gcc. Removing support for it in future Pythons would make problems involving MinGW build (like this one) much easier to solve in future: there would be no need to consider anything other than the behaviour of MinGW's gcc.

Content

I'm attaching one more patch "check_mno_cywin_py34.patch". This is my
preferred patch for Python 3.4 (default). It fixes building with MinGW
and removes all support for using Cygwin gcc with --compiler=mingw32.
The user would see the following error message:

'''
Q:\current\testing\hello>testbuild q:\tools\cygwin\bin -3.3
running build_ext
error: Cygwin gcc cannot be used with --compiler=mingw32
'''

I think that this is reasonable as '-mno-cygwin' is a previously
experimental and now long deprecated, discouraged and discontinued
feature of Cygwin's gcc. Removing support for it in future Pythons
would make problems involving MinGW build (like this one) much easier
to solve in future: there would be no need to consider anything other
than the behaviour of MinGW's gcc.

Files
File name	Uploaded
check_mno_cywin_py34.patch	oscarbenjamin, 2013-06-25.10:47:06

History
Date	User	Action	Args
2013-06-25 10:47:06	oscarbenjamin	set	recipients: + oscarbenjamin, lemburg, 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, fratti
2013-06-25 10:47:06	oscarbenjamin	link	issue12641 messages
2013-06-25 10:47:06	oscarbenjamin	create