Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > the compiling strategy for Python (IIRC) is to compile everything, > including modules that will never work, and use compiler errors as a > signal to not include a module in the result.
I don't think this can work in the cross-compilation case, though (or the entire setup.py part of it can't really work). It uses the target's python binary to run setup.py, compiles the modules, and then tries to load them. In a cross-compilation case, you can't run the target python binary, and even if you use a host python instead, you can't load the target extension modules (unless the "cross" compilation is for the same microprocessor and operating system - a case I'm not very much interested in). _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1597850> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
