Roumen Petrov added the comment:
For protocol - as requested patches attached to this issue are split ans posted
as separate issues.
Please follow those listed below:
issue18654 - modernize mingwcygwin compiler classes (new)
issue17605 - mingw-meta: build interpreter core
issue18653 -
Matthias Klose added the comment:
Ray Donnelly added the comment:
Next time there's a release of Python 3, I'll rebase my patches against that.
sorry, this is the wrong attitude, if you want mingw support to go upstream.
fetch tip/trunk, re-apply your patches, and submit them.
--
Matthias Klose added the comment:
now closing/rejecting this issue. See
http://mail.python.org/pipermail/python-dev/2013-January/123774.html
for the discussion.
--
resolution: - rejected
stage: patch review - committed/rejected
status: open - closed
Roumen Petrov added the comment:
Please do not post to this thread.
Follow python bugs list for result of patch-split. I will try to post parts of
this patch to already opened issues or to open new one if necessary.
As basis will be used py3k-20121004-MINGW.patch with following main changes:
-
Ray Donnelly added the comment:
Great Roumen, please split into new issues then make a new overall tracking
issue, then this one can be left for historians and archaeologists.
For Posix installation scheme I've got:
Ray Donnelly added the comment:
When I say “our patches” I mean mine and Alexey Pavlov’s jointly maintained
patch-set.
I hope you don’t mind that I find you saying:
I tried some of these patches, but they aren't very organinzed. I really need
some docemntaiton to better understand what each
Matthias Klose added the comment:
IMHO, updating these patches to track the latest Python is a pointless goal.
sorry, no. it's the *only* way to get these patches upstream. The mingw patches
will never see the light of the 3.3 branch. So the best thing to do is to
actively submit the patches
Matthias Klose added the comment:
However, we must go further and add that the patches *cannot* break any
other native or cross-compilation, which - as I think Matthias is
alluding to - is probably not the case with your patch. This issue is
called cross and native build of python for mingw*
Ray Donnelly added the comment:
Re: basing the patches against the latest master branch or targeting released
versions, I wasn't clear enough about my thinking.
For sure, when trying to get any patches merged, the submitted patch must be
re-based (forward ported) and tested against the master
Roumen Petrov added the comment:
Matthias Klose wrote:
Matthias Klose added the comment:
some random comments about py3k-20121004-MINGW.patch:
- Modules/_ctypes/libffi_msvc/win32.S
Please can you get rid of libffi_msvc and use libffi?
afaics, libffi has support for mingw32.
No
Giampaolo Rodola' added the comment:
This discussion got very long and it's not clear (to me at least) what the
status of the patch is and whether it has been accepted for inclusion.
Maybe it makes sense to bring this up to python-dev mailing list instead of
keep stressing this thread?
Ray Donnelly added the comment:
Roumen, I think it would be really great if you could split
py3k-20121004-MINGW.patch up into separate bits.
The pthread stuff and libffi stuff being two obvious candidates for atomic
parts.
--
___
Python tracker
Roumen Petrov added the comment:
As patch 0005-CROSS-revert-issue13150-i.e.-python-solution-with-_s.patch
(CROSS-revert issue13150, i.e. python solution with _sysconfigdata.py instead
Makefile) from issue3754 is now obsolete by issue 13547, 14774, 16342, 15298
it is save to switch
Luke Kenneth Casson Leighton added the comment:
the last time this was brought up on python-dev the opinions of the primary
python developers was made very very clear: anything that is not written by
them is treated with extreme hostile and predudicial contempt.
what i mean by that is that
Matthias Klose added the comment:
some random comments about py3k-20121004-MINGW.patch:
- Modules/_ctypes/libffi_msvc/win32.S
Please can you get rid of libffi_msvc and use libffi?
afaics, libffi has support for mingw32.
- there seem to be chunks which are unrelated to mingw, like:
@@
Jason Huntley added the comment:
Finally! I was able to get all building on mingw64, gcc 4.7.2, and python 3.3.
I had to take everybody's work here a little further, and I have produced a new
patch which will build python33 using the latest minw64 compiler in an msys
environment.
I cloned
Jason Huntley added the comment:
Hey Guys,
I've furthered the progress of the patch I've been working on. THis patch
builds Python3.3 in mingw64 msys using gcc 4.7.2 compiler. This patch can
also enable and build the following modules:
ctypes
bz2
multiprocessing
sqlite3
ssl
pyexpat
zlib
Of
Changes by Jason Huntley oneprem...@gmail.com:
Removed file: http://bugs.python.org/file28699/py3k-20121227-MINGW.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3871
___
Jason Huntley added the comment:
Hey Guys,
I've furthered the progress of the patch I've been working on. THis patch
builds Python3.3 in mingw64 msys using gcc 4.7.2 compiler. This patch can
also enable and build the following modules:
ctypes
bz2
multiprocessing
sqlite3
ssl
pyexpat
zlib
Of
Roumen Petrov added the comment:
Jason Huntley wrote:
Jason Huntley added the comment:
Finally! I was able to get all building on mingw64, gcc 4.7.2, and python
3.3. I had to take everybody's work here a little further, and I have
produced a new patch which will build python33 using the
Jason Huntley added the comment:
Finally! I was able to get all building on mingw64, gcc 4.7.2, and python 3.3.
I had to take everybody's work here a little further, and I have produced a new
patch which will build python33 using the latest minw64 compiler in an msys
environment.
I cloned
Ray Donnelly added the comment:
Good work Jason,
I think it would be great if everyone could collaborate better with this stuff;
I'm as guilty as the next person on that score though. I might have been able
to save you some effort by pointing you at either:
Roumen Petrov added the comment:
Jason Huntley wrote:
patch -t -p1 python-py3k-20120729-MINGW.patch
Please run autoheader (optional) and autoconf (required .
./configure --host=x86_64-w64-mingw32 --build=x86_64-w64-mingw32
--prefix=/mingw
...
--
Jason Huntley added the comment:
I'm attempting to build Python-3.3.0 with mingw64. I get a minute or two into
the build and fail with this error:
./Include/pythonrun.h:178:1: warning: function declaration isn't a prototype [-W
strict-prototypes]
./Modules/getpath.c: In function 'isfile':
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3871
___
___
Python-bugs-list
Roumen Petrov added the comment:
Extract of 2012-10-04 is after patch set py3k-20121004-CROSS.tgz from issue
#3754 .
--
title: cross and native build of python for mingw32 with packaging - cross and
native build of python for mingw* hosts
Added file:
26 matches
Mail list logo
