homepage

"Buildroot: Making Embedded Linux easy" has patches for Python 2.7 to simplify the cross-compilation of Python:
http://git.buildroot.net/buildroot/tree/package/python
The maintainer, Thomas Petazzoni, told me that the 12 first patches are the most important. Other patches are to disable some features.

buildroot-python-patches.tar.gz: today checkout of the git repository (package/python).

buildboot.patch: the 12 patches combined into a single patch for Python 2.7.
Note: python-2.7-001-support-for-build.patch doesn't apply cleanly on 
release27-maint.

Well, the patches should be first ported to 3.3 (and need checking that they don't break anything: test suite, etc.). Then, if you want them to be examined separately, it might be better to create a separate issue for each.

I uploaded the patch to Rietveld for a review:
http://codereview.appspot.com/4253047
> Well, the patches should be first ported to 3.3
Ok, I will ask the author if he can do this job. I uploaded the patches for Python 2.7 for a review and to open the discussion.

All is duplicate on already posted patches . It is not work to review limited functionality posted here.

A quick search gives me:
- #1006238
- #1597850
- #3754
- #5404
- #3871
Are they the same patches from Buildroot?

No, they’re not the same.
See also my listing of (most of the) cross-compile patches: http://mail.python.org/pipermail/python-dev/2011-March/110099.html 

The distutils changes will not happen, we’re under a feature freeze. Cross-compilation support would need to be added to packaging, and we need to port Python’s build process to packaging too for 3.4 or 3.5. Also, it’s very hard to decide to accept one solution from the dozen of different patch sets posted on the various issues. I think this would need a concerted effort from all people who have worked on patches, with goals clearly defined in a public mailing list, then python-dev agreement (including MvL, who turns a very critical eye to such patches), then one patch satisfying the requirements.
I don’t like to reject the hard work of contributors who want to give back, but given the situation I describe above I’m inclined to close all of these bugs for now.

> The distutils changes will not happen, we’re under a feature freeze.
> Cross-compilation support would need to be added to packaging, and we
> need to port Python’s build process to packaging too for 3.4 or 3.5.
Why 3.4 or 3.5?

Because I don’t think anyone will have the time to try to port Python’s setup.py to packaging, fix the bugs it founds and add the features it needs in time for 3.3. On my own todo lists, there is much work still needed to define the public API, add features we want, test it with real applications such as pip, fix major bugs, make the docs usable.

@doko: You integrated patches related to cross-compilation. Can this issue be closed, or does the Buildroot project still contain useful patches?