[issue4954] native build of python win32 using msys under wine.

Leonard Ritter added the comment: Hello everyone, I'm seconding the wish to be able to build Python with MSYS on Win32, and I can give several technical reasons: It is my understanding that in order to build an extension for Python on Win32, one requires to use the same compiler as the one Pyt

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: martin, so sorry, i didn't see your comments - no dang hell no i'm not done yet. regarding graminit.h: graminit.h isn't being removed - i keep editing it out of the patch. i'm not _submitting_ it as part of the patch because what happens is that P

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: manifests and rc files for msvcr80 build Added file: http://bugs.python.org/file12830/x ___ Python tracker ___ ___

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: updated. incorporating roumen's work as well. Added file: http://bugs.python.org/file12826/f ___ Python tracker ___ __

[issue4954] native build of python win32 using msys under wine.

Changes by Martin v. Löwis : -- nosy: -loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue4954] native build of python win32 using msys under wine.

Changes by Luke Kenneth Casson Leighton : Removed file: http://bugs.python.org/file12764/x ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: workarounds for a couple of wine bugs, also includes e.g. #4977 64-bit assumptions on 32-bit systems. Added file: http://bugs.python.org/file12780/f ___ Python tracker __

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: I'm rejecting this patch for the moment, as it seems far from being ready yet. If you consider it complete and applicable-as-is (i.e. if you can't think of any possible further improvement to the patch), please submit a new issue. If I had to review the patch "

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: http://www.winehq.org/pipermail/wine-users/2006-May/021624.html _drat_. a rebuild of wine, adding a workaround to cope with lack of support for msvcrt80 xml-based process files, is required, commenting out a couple of functions from kernel32! eu

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: > 2) there is no .exe so i was forced to install from msi, >a proprietary installer - which as a free software >developer, i have issues with, but i tried it anyway. Please understand that MSI is *not* a proprietary installer. Instead, it is just a da

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: yaay! here's the regression test log, including some loovely wine segfaults :) summary: 250 tests OK. 12 tests failed: test_builtin test_cpickle test_file test_gzip test_locale test_mailbox test_os test_pep277 test_socket test_unicode_f

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: > It is certainly desirable to be able to build extension modules > with this configuration; yeah, and the nice thing is - it works, too! :) > AFAIU, distutils already supports that case. not without modification, it doesn't: #3871 adds "prope

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: > So what CRT do you link with? Is it msvcrt? Which version? i was _just_ beginning to wonder about that, after i saw rpetrov's comments about MSCVER stuff. http://www.mingw.org/wiki/SpecsFileHOWTO aww, _frick_. :) well... it's _going_ to be ms

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: > Please trust that Python puts generated files into the repository for > good reasons. i can respect that :) for no reason other than if somone says "please trust", i do :) ___ Python tracker

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: > no more proprietary dependence. So what CRT do you link with? Is it msvcrt? Which version? If building with mingw becomes wide-spread, care must be taken that it uses the same CRT as the official binaries. Otherwise, it will be a desaster for Python.

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: > * graminit and configure were removed because they are built > automatically. no project should ever include auto-generated files so i > assumed that it would be reasonable to remove them from the python_2.5.2 > "original" git commit that i did, in order to

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: > Is Msys+Mingw32 (running on a regular Windows) an interesting > configuration to support? It is certainly desirable to be able to build extension modules with this configuration; AFAIU, distutils already supports that case. Whether or not it is desirable to

[issue4954] native build of python win32 using msys under wine.

Changes by Luke Kenneth Casson Leighton : Removed file: http://bugs.python.org/file12755/f ___ Python tracker ___ ___ Python-bugs-list mailing

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: updated patch - also removes quotes removal quotes of graminit and configure so that martin is happier :) also included is an updated version of #4956 as it's an essential integral part of compiling and using python.exe under msys that it actually

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: hi amaury, thanks for responding. > Is Msys+Mingw32 (running on a regular Windows) an interesting > configuration to support? [wine+]msys+mingw32 is used to _build_ python - not depend on it. [wine+]msys+mingw32 _replaces_ the proprietary build

[issue4954] native build of python win32 using msys under wine.

Luke Kenneth Casson Leighton added the comment: martin, hi, thanks for responding. * graminit and configure were removed because they are built automatically. no project should ever include auto-generated files so i assumed that it would be reasonable to remove them from the python_2.5.2 "orig

[issue4954] native build of python win32 using msys under wine.

Amaury Forgeot d'Arc added the comment: Is Msys+Mingw32 (running on a regular Windows) an interesting configuration to support? The build tools are similar to the ones used by cygwin, except that the C runtime is msvcrt. -- nosy: +amaury.forgeotdarc

[issue4954] native build of python win32 using msys under wine.

Martin v. Löwis added the comment: Are you seriously requesting inclusion of the file f into Python? It contains many changes that are unsuitable for inclusion, such as the removal of graminit.c and the removal of configure. (besides, I personally think that the ability to compile Python with m

[issue4954] native build of python win32 using msys under wine.

Changes by Luke Kenneth Casson Leighton : -- type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue4954] native build of python win32 using msys under wine.

New submission from Luke Kenneth Casson Leighton : this patch uses work from #3871 to get a build of python for win32 by running msys under Wine, the windows emulator, on linux. no proprietary operating system or proprietary software was used. /bin/sh.exe is so ing unbelievably slow on msys