This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hohjg
Recipients
Date 2003-11-27.08:17:58
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=359136

Ok, here comes my patch (for python version 2.3.2) 
 
For the Makefile: It introduces a new Variable HOSTPYTHON; this is 
initially set to BUILDPYTHON, but for crosscompilation purposes it 
should be set to name of a python binary, which runs on the build 
machine. 
In calls to setup.py the variable CROSS_COMPILATION is set to "yes". 
 
In the setup.py we check for the value of CROSS_COMPILATION; if 
not set to "yes" , LIBDIR and INCLUDEDIR are taken from calls to 
distutils, otherwise we get it from the corrsponding environment 
variables (but the Makefile doesn't export them, because I don't need 
them anymore).  
 
In all cases don't add /usr/lib/, /usr/include and /lib to the search pathes 
of the compiler, because these pathes are searched first for include files 
and libraries (before the default path settings from the compiler; so a 
crosscompiler will always use the host includes instead of the includes 
of the target plattform). 
 
Here (http://www.ailis.de/~k/knowledge/crosscompiling/python.php) is 
described how to use that Makefile. 
 
Please note: This patch works for me, and probably it isn't usefull to 
include it into the distribution. But please look at the changes of the 
include and library pathes, they won't affect all the native builders, but 
may help alot of people who do crosscompiling. 
 
History
Date User Action Args
2008-01-20 09:59:30adminlinkissue848910 messages
2008-01-20 09:59:30admincreate