bkc at Murkworks.com
Tue Jun 29 20:33:48 CEST 2004
"Alexander May" <alex-news-deleteme at comcast.net> wrote in message
news:55iEc.112810$2i5.78663 at attbi_s52...
> > I doubt you'll need to do much "porting". Unless the Linices you
> > are considering are quite unusual, they ought to look a lot like any
> > other Linux, and Python may well work largely unchanged.
> from http://www.vanille.de/projects/python.spy (from Christopher T King's
> "You won't find many Python distributions for arm-linux, because Python is
> pretty finnicky when it comes to cross-compiling. The build process of
> Python compiles a core part of it (the parser generator pgen) and tries to
> execute that later in the build process. This - of course - doesn't work
> cross compiling. My patches to the Python build scripts are available @
> sourceforge and are likely to be included into the main Python tree."
Don't worry about this. I've ported Python to a 68K board (8 meg ram, 4 meg
flash) running uClinux. That was a squeeze, due to uClinux limitations I had
to statically link in libxml2, libxslt and other goodies I needed.
It worked, and the build process was easy to tidy up (once you know how it
works). I cross compiled from RH9 (386) using gcc tools. Put the binaries on
NFS and tested from the 68K box. Later, burned a flash rom image with the
More information about the Python-list