[issue4709] Mingw-w64 and python on windows x64

Change by Irit Katriel : -- resolution: duplicate -> wont fix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4709] Mingw-w64 and python on windows x64

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> MinGW is unsupported - close all open issues and list them here. ___ Python tracker

[issue4709] Mingw-w64 and python on windows x64

Changes by Ivan Pozdeev : -- nosy: -Ivan.Pozdeev ___ Python tracker ___ ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Berker Peksag : -- Removed message: http://bugs.python.org/msg263481 ___ Python tracker ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Berker Peksag : -- Removed message: http://bugs.python.org/msg263480 ___ Python tracker ___

[issue4709] Mingw-w64 and python on windows x64

Ivan Pozdeev added the comment: I know it's a wiki but I couldn't edit the page even after I registered, so I thought It's protected. I'll try the e-mail now. -- nosy: +Ivan.Pozdeev ___ Python tracker

[issue4709] Mingw-w64 and python on windows x64

Ivan Pozdeev added the comment: Whoops, wrong ticket. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: Hi all, There is now a much more concrete plan for the static MinGW-w64 based toolchain, and the first funding has materialized. Please see the announcement on the Numpy mailing list (http://article.gmane.org/gmane.comp.python.numeric.general/62207), the

[issue4709] Mingw-w64 and python on windows x64

Changes by matham : -- nosy: +matham ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Nathaniel Smith added the comment: > We are working on the Fortran issue in a few different ways, one of which is > your work on MinGW compatibility so that gfortran can be used. But that isn't > the only solution to this whole problem, and it's not even preferable for a > lot of Python

[issue4709] Mingw-w64 and python on windows x64

Steve Dower added the comment: "We" is a lot of different companies and individuals. Anyone distributing prebuilt binaries is helping here, a few people are working on the licensing concerns for some components, other people are working on C BLAS libraries. I see the issue approximately as

[issue4709] Mingw-w64 and python on windows x64

Nathaniel Smith added the comment: Hi Steve- okay, thanks for clarifying! I think you already know this, but for the general record: the reason for the apparent fixation on this solution is that after a lot of struggle it's emerged as basically the only contender for

[issue4709] Mingw-w64 and python on windows x64

Steve Dower added the comment: And FTR, there are plenty of major Python-using companies that insist on compiling from scratch and also refuse to touch GPL at all, no matter how many exemptions are in the licenses. GFortran is not the ideal solution for these users. --

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: > "We" is a lot of different companies and individuals. Anyone distributing > prebuilt binaries is helping here, a few people are working on the licensing > concerns for some components, other people are working on C BLAS libraries. Note that we by default

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: > I'm happy and keen to help so please feel free to poke me if you need > assistance with anything. I'll keep an eye out too - is it actively being > discussed on any list? Thanks Henry. There's no ongoing discussion on a list right now, but give it a week or

[issue4709] Mingw-w64 and python on windows x64

Steve Dower added the comment: We are working on the Fortran issue in a few different ways, one of which is your work on MinGW compatibility so that gfortran can be used. But that isn't the only solution to this whole problem, and it's not even preferable for a lot of Python users, so expect

[issue4709] Mingw-w64 and python on windows x64

Henry Gomersall added the comment: Thanks Ralf - I'm happy and keen to help so please feel free to poke me if you need assistance with anything. I'll keep an eye out too - is it actively being discussed on any list? -- ___ Python tracker

[issue4709] Mingw-w64 and python on windows x64

Steve Dower added the comment: As an occasional Linux user, I notice a huge difference between pure Python and extension packages there, but basically always have a compiler handy on my Windows machines. It's all about context and what you're used to :) The advice has always been "Visual

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: > @Steve Great, so what needs to be done so that I as a package developer can > do `pip install windows-build-system`, `python setup.py bdist_wheel` and it > actually creates a wheel? (which AFAICT is the same problem). Hi Henry, I expect progress on the

[issue4709] Mingw-w64 and python on windows x64

Henry Gomersall added the comment: @carlkl right, but it's not really a seamless experience. I think my question is: What needs to still be done in order that a user with a fresh Python install in Windows (and no compiler installed) can do "pip install an_extension_that_needs_compiling" and

[issue4709] Mingw-w64 and python on windows x64

Steve Dower added the comment: > What needs to still be done in order that a user with a fresh Python install > in Windows (and no compiler installed) can do "pip install > an_extension_that_needs_compiling" and it _just works_? The package developer takes the time to build a wheel on Windows

[issue4709] Mingw-w64 and python on windows x64

Henry Gomersall added the comment: @Steve Great, so what needs to be done so that I as a package developer can do `pip install windows-build-system`, `python setup.py bdist_wheel` and it actually creates a wheel? (which AFAICT is the same problem). My interest is precisely as a package

[issue4709] Mingw-w64 and python on windows x64

Changes by Zachary Ware : -- nosy: +zach.ware ___ Python tracker ___ ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Nathaniel Smith : -- nosy: +njs ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Carl Kleffner added the comment: The situation is not THAT bad. You can install a prerelease of mingwpy with pip: pip install -i https://pypi.anaconda.org/carlkl/simple mingwpy or with conda: (thanks to omnia-md) conda install -c https://conda.anaconda.org/omnia mingwpy It is not hosted

[issue4709] Mingw-w64 and python on windows x64

Henry Gomersall added the comment: Of course, I mean: *To be clear, the MinGW situation surely cannot be worse than the current situation.* -- ___ Python tracker

[issue4709] Mingw-w64 and python on windows x64

Changes by Duncan McBryde : -- nosy: +Duncan McBryde ___ Python tracker ___ ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Stefano Taschini : -- nosy: +taschini ___ Python tracker ___ ___

[issue4709] Mingw-w64 and python on windows x64

Changes by Steve Dower steve.do...@python.org: -- nosy: +steve.dower ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Ruben Van Boxem added the comment: Paul, Thank you for your serious take on the issue. I'm Ruben, a long-time contributor and 3-ish year toolchain builder for MinGW-w64. I originally helped patching Qt 4.5/4.6 so that it worked with MinGW-w64 on 64-bit Windows. I can help liaison between

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: Ruben, Thanks for the detailed explanations. Just to be clear, I am *not* the person that will take this aspect of the process forward - that will be the community of people building (or wanting to build) extensions for Python with mingw. I don't know if that

[issue4709] Mingw-w64 and python on windows x64

Ruben Van Boxem added the comment: Paul, OK, I understand your point of view. As you say, there is no single MinGW community, nor a guiding body that takes these decisions. If you're not willing to choose one, all I can say is this: it will probably not matter which version you choose (all

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: Indeed, our idea of easy to install was/is a wheel or set of wheels so that pip install mingw64py does all you need. If necessary that can of course be repackaged as single download to unzip as well. -- ___ Python

[issue4709] Mingw-w64 and python on windows x64

Changes by Case Van Horsen cas...@gmail.com: -- nosy: +casevh ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: If there is no interest in having a (community-supported, semi- official) GCC-built Python on Windows, I'm sure something else can also be worked out, which would include stripping the current dinosaur -mno-cygwin code which is what this bug was originally all

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: On 19 May 2015 at 17:09, Руслан Ижбулатов rep...@bugs.python.org wrote: 3) Use MSVC for CPython and MinGW-w64 for the rest and somehow ensure that FDs are converted when passing the CRT barrier. And stat structs as well. And everything else that differs. This

[issue4709] Mingw-w64 and python on windows x64

Ralf Gommers added the comment: A few comments from the perspective of what's needed for the scientific Python stack: 1. Of the three options mentioned in msg243605, it's definitely (3) that is of interest. We want to build extensions with MinGW-w64 that work with the standard MSVC Python

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: Ralf, thanks for the comments. The scientific community is definitely the key group that *need* mingw (as opposed to people who merely want to use it because they don't want to buy into MS compilers, or for similar personal reasons). My personal view is that if

[issue4709] Mingw-w64 and python on windows x64

R. David Murray added the comment: My understanding matches yours, Paul. Core does not want to *distribute* a mingw built python, but if the mingw community came up with a support strategy, including one or more buildbots building using mingw, I believe that we would accept the patches.

[issue4709] Mingw-w64 and python on windows x64

Руслан Ижбулатов added the comment: If there is no interest in having a (community-supported, semi- official) GCC-built Python on Windows, I'm sure something else can also be worked out, which would include stripping the current dinosaur -mno-cygwin code which is what this bug was originally

[issue4709] Mingw-w64 and python on windows x64

Ismail Donmez added the comment: Still a problem with mingw-w64 gcc 5.1 and Python 3.4.3, time to fix this? -- nosy: +cartman ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___

[issue4709] Mingw-w64 and python on windows x64

Ralf Schmitt added the comment: Well, the time to fix this would have been six years ago. The python core developers have shown a disinterest to fix problems with gcc on windows for a rather long time. I wouldn't expect this issue to be fixed. --

[issue4709] Mingw-w64 and python on windows x64

Changes by Ralf Schmitt python-b...@systemexit.de: -- nosy: -schmir ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: Not at all. Mingw support is important for the scientific community, as I understand it, and I'm willing to help there if I can. That won't be at the cost of other areas I can contribute to, but I consider packaging as much my area of expertise as Windows - and

[issue4709] Mingw-w64 and python on windows x64

Giampaolo Rodola' added the comment: For what it's worth I dropped support for mingw32 in psutil for exact the same reasons. As such I cannot imagine how hard could it be to add and maintain support for mingw in a much larger project as Python. --

[issue4709] Mingw-w64 and python on windows x64

R. David Murray added the comment: Please note that Paul is pretty new to the core team, and is a crossover with the packaging folks (which is mainly where the mingw issues lie). What this means to the mingw community is that with Paul on the core team and willing to work on the support, the

[issue4709] Mingw-w64 and python on windows x64

Mark Lawrence added the comment: Does this mean scarce Windows resources being diverted off to what I consider a side show? Unless it's categorically stated that mingw is officially supported in which case fine, provided the experts index and everything else associated with official support

[issue4709] Mingw-w64 and python on windows x64

Paul Moore added the comment: Supporting mingw building of extensions has always been a complicated process, mainly because there appear to be many variants of mingw (and in particular, there seem to be multiple 64-bit builds). Add to this the fact that cygwin is sometimes used as a

[issue4709] Mingw-w64 and python on windows x64

Mark Lawrence added the comment: Hunting around I found this on #3871 https://mail.python.org/pipermail/python-dev/2013-January/123774.html. From #17590 upwards there are perhaps 25 issues with mingw in the title, so there's certainly work to be done. Please don't look at me, I'm simply not

[issue4709] Mingw-w64 and python on windows x64

Simon Zack added the comment: The problem is still present in python 3.4 with mingw gcc 4.8.2. I was having trouble with compiling radare2's python swig bindings. The solution described here: http://ascend4.org/Setting_up_a_MinGW-w64_build_environment#Setup_Python_for_compilation_of_extensions

[issue4709] Mingw-w64 and python on windows x64

Changes by Ralf Gommers ralf.gomm...@gmail.com: -- nosy: +ralf.gommers ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Alex added the comment: I want to add that this bug led to bizarre behavior (described here: http://stackoverflow.com/questions/18646694/pass-pointer-from-c-to-python-w-boost-python) when using 64-bit Boost-Python compiled with Mingw-w64 in Windows 7. Boost-Python and programs linked to it

[issue4709] Mingw-w64 and python on windows x64

John Pye added the comment: This bug is still present in Python 2.7.5 on Windows 64-bit . I am currently providing the following instructions for MinGW-w64 users wanting to link to Python27.dll:

[issue4709] Mingw-w64 and python on windows x64

Changes by Roumen Petrov bugtr...@roumenpetrov.info: -- nosy: +rpetrov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Ralf Schmitt python-b...@systemexit.de added the comment: Marting, this issue is about building python extensions with mingw-w64 not about building python itself. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709

[issue4709] Mingw-w64 and python on windows x64

John Pye j...@curioussymbols.com added the comment: Martin, Ralf is right and my as previously linked is about building a python extension. I should have been more explicit about that. FWIW I found that the configure scripts on MinGW-w64 generally work fine if you add a

[issue4709] Mingw-w64 and python on windows x64

Ralf Schmitt python-b...@systemexit.de added the comment: There's no need to discuss or even run configure scripts. Martin, please reread the OPs original message. It's easy enough to reason about the issue instead of trying to reproduce it. -- ___

[issue4709] Mingw-w64 and python on windows x64

John Pye j...@curioussymbols.com added the comment: Hi Martin I have documented a build process for a Python package on MinGW-w64, including a requirement that this patch be applied. You might want to revisit it, given that your attempt to reproduce this bug earlier was unsuccessful.

[issue4709] Mingw-w64 and python on windows x64

Martin v. Löwis mar...@v.loewis.de added the comment: John: in the current versions of the toolchain, Python's configure fails for me. I follow steps 1..3 of Steps to date. Then running ./configure fails saying that it does not work. I then tried alternatively these three approaches: 1. set

[issue4709] Mingw-w64 and python on windows x64

Ralf Schmitt sch...@gmail.com added the comment: I'm also using this patch successfully (together with http://tdm-gcc.tdragon.net/). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709

[issue4709] Mingw-w64 and python on windows x64

Changes by René Schümann whitet...@gmail.com: -- nosy: +WhiteTiger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Ruben Van Boxem vanboxem.ru...@gmail.com added the comment: Has anyone looked at this? I'm trying to build gdb with Python enabled with mingw-w64 (Python 2.7.1 with manually created import libraries), but have to manually define MS_WIN64 in the CFLAGS. The patch only does what's right (i.e.

[issue4709] Mingw-w64 and python on windows x64

Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___

[issue4709] Mingw-w64 and python on windows x64

cournapeau david courn...@gmail.com added the comment: Hi Martin, It was nice meeting you at Pycon. I finally took the time to set up a windows 64 bits environment, and here are the exact steps I needed to do to reproduce the issue, and fix it by hand: - Start fresh from windows 7 64 bits

[issue4709] Mingw-w64 and python on windows x64

Changes by Ralf Schmitt sch...@gmail.com: -- nosy: +schmir ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Changes by Christoph Gohlke cgoh...@uci.edu: -- nosy: +cgohlke ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list mailing

[issue4709] Mingw-w64 and python on windows x64

Changes by Scott Tsai scottt...@gmail.com: -- nosy: +scott.tsai ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___ Python-bugs-list

[issue4709] Mingw-w64 and python on windows x64

Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709 ___ ___

[issue4709] Mingw-w64 and python on windows x64

Martin v. Löwis mar...@v.loewis.de added the comment: I have now tried reproducing the problem, and still failed to. I downloaded, from http://sourceforge.net/projects/mingw-w64/files/, the distribution mingw-w32-bin_i686-mingw_20100123_sezero.zip. With this, I get

[issue4709] Mingw-w64 and python on windows x64

Cournapeau David da...@ar.media.kyoto-u.ac.jp added the comment: Ok, it looks like following gcc 4.4.0 release, there is an installer for the whole toolchain: http://www.equation.com/servlet/equation.cmd?call=fortran This installs gcc (C+Fortran+C++ compilers, the download is ~ 40 Mb), and it

[issue4709] Mingw-w64 and python on windows x64

Martin v. Löwis mar...@v.loewis.de added the comment: The toolchain is difficult to build, but the patch is easy to review, it just moves the MS_WIN64 outside the MS compiler specific part. If it does not break the MS toolchain (the one used to build the official python), I don't see the

[issue4709] Mingw-w64 and python on windows x64

Martin v. Löwis mar...@v.loewis.de added the comment: Lowering the priority. It's too difficult to setup the environment to be able to reproduce the issue being fixed. -- priority: critical - normal ___ Python tracker rep...@bugs.python.org

[issue4709] Mingw-w64 and python on windows x64

Cournapeau David da...@ar.media.kyoto-u.ac.jp added the comment: The toolchain is difficult to build, but the patch is easy to review, it just moves the MS_WIN64 outside the MS compiler specific part. If it does not break the MS toolchain (the one used to build the official python), I don't see

[issue4709] Mingw-w64 and python on windows x64

Cournapeau David da...@ar.media.kyoto-u.ac.jp added the comment: Is there any change to see this integrated soon ? The patch is only a couple of lines long, thanks -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4709

[issue4709] Mingw-w64 and python on windows x64

Martin v. Löwis mar...@v.loewis.de added the comment: Can you please provide some setup instructions for mingw-w64? What URLs should I install in what order, so that I can compile Python? -- ___ Python tracker rep...@bugs.python.org

[issue4709] Mingw-w64 and python on windows x64

New submission from Cournapeau David da...@ar.media.kyoto-u.ac.jp: I believe the current pyport.h for windows x64 has some problems. It does not work for compilers which are not MS ones, because building against the official binary (python 2.6) relies on features which are not enabled unless