On 7/24/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> The main problem is that it is the host python that runs setup.py,
> not the target python. Various parts of distutils assume that the
> information the interpreter provides is correct, yet it is not
> in a cross-compilation case.
Well, it
Ed Swierk wrote:
> Well, it seems buildroot solves this main problem by building another
> version of python and pygen that run on the build machine, and hacks
> the Makefile to run setup.py with these instead of whatever happens to
> be sitting in /usr/bin.
If you think its useful, please submit
Ed Swierk wrote:
> I decided to hack up setup.py so that an optional root directory (passed via
> an
> environment variable) is prepended to all the hardcoded paths like
> "/usr/include", "/lib", "/lib64", and so on.
I doubt this solves the problem. Distutils just doesn't support
cross-compilatio
I'm cross-compiling Python using uClibc buildroot, which installs target include
files and libraries to a directory like ~/toolchain rather than /usr. I
couldn't figure out any way to convincing the top-level python/setup.py to look
in ~/toolchain instead of /usr when detecting what modules to bui
