[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: May be patch 20120729 cannot be applied as my source tree contain a number of patches related to cross build - see msg166740 from issue 3754 . -- Added file: http://bugs.python.org/file26572/python-py3k-20120729-MINGW.patch

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: Thanks Matthias, I might wait until b2 (or rc1) before I rebase my patches, just because I'm so unfamiliar with Mercurial. -- ___ Python tracker

[issue3871] cross and native build of python for mingw32 with packaging

Matthias Klose added the comment: fyi, the cross build changes are now checked in. Checked with an x86_64-linux-gnu to arm-linux-gnueabi cross build. I don't plan to add anything more for the 3.3 release besides bug fixes. -- ___ Python tracker <

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: I'm not personally interested in Cygwin (it's too slow for my liking) and I've spent a lot of time patching and building software to avoid forcing people to use it (no offence meant to Cygwin people, I can see the value of it, but IMHO native is always best) .

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: For me, it's all about being able to build useful software. I like Python a lot, but my goal is and has always been cross compilation of gdb with Python support. To that end, if I have to maintain some out of tree patches for 2.7.3 then so be it. For 3.x things

[issue3871] cross and native build of python for mingw32 with packaging

Luke Kenneth Casson Leighton added the comment: > The feature freeze applies to all branches. Even when 3.4 starts, the > same rule that has been repeatedly explained for two years will apply: > no new features in distutils. Again, neither Tarek nor I are happy > about that, but it was the d

[issue3871] cross and native build of python for mingw32 with packaging

Luke Kenneth Casson Leighton added the comment: > distutils2 is the place to add such new features. you're not getting it. you've just told both this mingw32 project and also the new effort by ray that they can go fuck themselves, because their efforts are a total waste of time (as far as pyt

[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: Hi Mattias , I have ready to upload patches for 3.3.30b1 but after recent changes I will postpone upload . Part of already uploaded patch cover cygwin native build . For instance a) --enable-new-dtags is only for elf binaries. b) use of libpython$(LDVERSION),

[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: Eric. please could could you revert PEP 405 as distutils is frozen or step down as It seems to me you don't flow distutils evolution. -- ___ Python tracker

[issue3871] cross and native build of python for mingw32 with packaging

Éric Araujo added the comment: > Not sure if they will go into 3.3, because there seem to be non-trivial > changes for in Lib/distutils. The feature freeze applies to all branches. Even when 3.4 starts, the same rule that has been repeatedly explained for two years will apply: no new feature

[issue3871] cross and native build of python for mingw32 with packaging

Matthias Klose added the comment: the cross build support is now updated for 3.3. so the mingw32 patches need an update. Not sure if they will go into 3.3, because there seem to be non-trivial changes for in Lib/distutils. Other self-contained changes probably should still go into 3.3. -

[issue3871] cross and native build of python for mingw32 with packaging

Éric Araujo added the comment: > I thought that the distutils-is-frozen rule was only for Python 2.x > and that they would be allowed for 3.x? Is this not true? It is not. The normal rule is that stable versions (like 2.7) get only bug fixes while new features go only to the development versio

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: Thanks for the details. I've got more fixes but I want to get the whole thing building (at least) before I post them. -- ___ Python tracker ___ _

[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: Ray , about python cygwin/mingw compiler classes exists other requests - use cygwin class instead unix compiler, remove relict checks : nocygwin and etc. but without progress. About merge of getpath sources - issue is 9654. -- _

[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: Correction: Use of relict alarm function is not excluded even failure in one of tests - the test is run if exist alarm function but require in addition SIGALARM attribute. -- ___ Python tracker

[issue3871] cross and native build of python for mingw32 with packaging

Roumen Petrov added the comment: Also include mingw-w64 fixes - check for structure REPARSE_DATA_BUFFER, use lower case names of some headers . set_abort_behavior. I prefer to exclude use of parse_off_t so that functionality to be to same. Use of relict alarm function is not excluded as one o

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: Hi Éric, Do you mean this bit?: diff -urN a/Lib/distutils/cygwinccompiler.py b/Lib/distutils/cygwinccompiler.py --- a/Lib/distutils/cygwinccompiler.py 2012-05-30 07:33:00.234438631 +0100 +++ b/Lib/distutils/cygwinccompiler.py 2012-05-30 07:33:03.320855811 +010

[issue3871] cross and native build of python for mingw32 with packaging

Éric Araujo added the comment: Thanks for your work Ray, but as your patch adds a feature to distutils it cannot be accepted. -- ___ Python tracker ___ _

[issue3871] cross and native build of python for mingw32 with packaging

Ray Donnelly added the comment: Although mainly focussed on MinGW, I've begun adding Darwin cross support. I've also built Darwin cross compilers. The latest Linux version can be found at: http://mingw-and-ndk.googlecode.com/files/multiarch-darwin11-cctools127.2-gcc42-5666.3-llvmgcc42-2336.1-L

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Ray Donnelly : Removed file: http://bugs.python.org/file25764/python-py3k-20120318-MINGW-330a2.patch ___ Python tracker ___ ___ Pyt

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Ray Donnelly : Added file: http://bugs.python.org/file25764/python-py3k-20120318-MINGW-330a2.patch ___ Python tracker ___ ___ Pytho

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Ray Donnelly : Added file: http://bugs.python.org/file25761/python-py3k-20120318-MINGW-330a2.patch ___ Python tracker ___ ___ Pytho

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Roumen Petrov : Added file: http://bugs.python.org/file24924/python-py3k-20120318-MINGW.patch ___ Python tracker ___ ___ Python-bugs

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Matthias Klose : -- components: +Cross-Build -Build, Distutils2 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue3871] cross and native build of python for mingw32 with packaging

Changes by Zooko O'Whielacronx : -- nosy: -zooko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue3871] cross and native build of python for mingw32 with packaging

Éric Araujo added the comment: > if you recall there was some discussion that it was acceptable to use > distutils but *only* for python 2.N There was discussion, yes, but it was not decided to change our decision on the freeze: msg121097 > just as an aside: have all python 3.N packaging scrip

[issue3871] cross and native build of python for mingw32 with packaging

Luke Kenneth Casson Leighton added the comment: eric, if you recall there was some discussion that it was acceptable to use distutils but *only* for python 2.N (on the basis that its use is so well entrenched that it would be impossible to force python2.N applications to start using distutil

[issue3871] cross and native build of python for mingw32 with packaging

Éric Araujo added the comment: Please read msg136382 and take it into account. Also, I suggest you wait a bit for packaging patches: GSoC projects need to be reviewed and integrated, which may change large parts of the codebase. -- title: cross and native build of python for mingw32