New submission from Trevor Bowen:
FWIW, I'm using a Freescale cross-compile tool-chain on a Linux x86-64 build
host, although I have duplicated the cross-compile error on an x86 Ubunutu
10.04 build host.
Steps to reproduce:
$ wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.ta
Trevor Bowen added the comment:
Sorry, I do not mean to compound an already open and complex problem. I
thought that the fixes in 2.7.4 were meant in part to help alleviate this
problem. I had not found any feedback or tutorials, so I wanted to provide a
status update of sorts. I'm
Trevor Bowen added the comment:
Ok, thanks for the tips. I'm new to developing on Python itself. I'll start
simple by trying to develop a set of patches for the 2.7.5 source tar-ball,
which I usually use to build Python. If that succeeds, I'll look into pushing
it into the
Trevor Bowen added the comment:
In the vein of:
http://randomsplat.com/id5-cross-compiling-python-for-embedded-linux.html
I have created a patch and top-level build script, which builds the requisite
python interpreter and Parser/pgen binary to run on the build system, which are
both used
Trevor Bowen added the comment:
Short version of cross-compile script without error checking:
#!/bin/bash
export RFS=/local/my_root_file_system
make distclean
rm -rf python_for_build Parser/pgen_for_build
git checkout -- Makefile.pre.in Modules/Setup.dist configure setup.py
./configure
make
Trevor Bowen added the comment:
FWIW, I also explored my original proposal, which essentially moved the above
script and modifications into the Python configure.ac and Makefile.pre.in
files, so that Python's internal build process would create the native build
system versions of Pytho
Trevor Bowen added the comment:
I thought "make touch" was only for those trying to build from the Mecurial
source, as opposed to building from the released tar-ball source. I thought my
efforts laid on the other side of the need for that command. If I understood
wrong, when woul
Trevor Bowen added the comment:
Thanks, David! I have no interest in running pgen on the target/host. My only
interest is building python and its various modules to run on my embedded host.
I do not want to develop Python on the embedded host. Unfortunately, the
build process requires
Trevor Bowen added the comment:
I executed "make touch" between "configure" and "make", but the build process
still created Parser/pgen and then tried to use it, which of course crashed the
build, since pgen was compiled for the embedded host not the build sy
