在我的Linux x86_64主机上,我想为我的PowerPC目标交叉编译一些额外的Python模块,具体来说就是greenlet,gevent,gevent-websockets。目前,我只是试图交叉构建greenlet模块。Python的greenlet和gevent在Linux x86_64上对于PowerPC的交叉编译
使用信息从这个站点:使用此设置为我的编译环境
# Undo variables for cross-compile environment
unset ROOT
unset SDKDIR
unset KLIBDIR
unset NFSDIR
unset CONFIG
unset CONFIGURED
unset ARCH
unset OS
unset TOOLCHAIN_BASE
unset TOOLCHAIN_BIN
unset CROSS_COMPILE
unset c
unset KERNEL_DIR
unset AS
unset LD
unset CC
unset AR
unset STRIP
unset SSTRIP
unset OBJCOPY
unset OBJDUMP
unset MAKE
unset CFLAGS
# Set cross-compile variables:
export TOOLCHAIN=/opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-2/powerpc-none-linux-gnuspe/bin/powerpc-none-linux-gnuspe-
export CC=${TOOLCHAIN}gcc
export CXX=${TOOLCHAIN}g++
export AR=${TOOLCHAIN}ar
export RANLIB=${TOOLCHAIN}ranlib
export BLDSHARED="${TOOLCHAIN}gcc -shared"
export LDSHARED="${TOOLCHAIN}gcc -shared"
export RFS="../../ltib/rootfs"
export CFLAGS="-save-temps -Wall -I${RFS}/usr/include -I${RFS}/include/python2.7 -L${RFS}/usr/lib -L${RFS}/lib"
export LDFLAGS="-I${RFS}/usr/include -I${RFS}/include/python2.7 -L${RFS}/usr/lib -L${RFS}/lib"
export CROSS_COMPILE=ppc-linux
export CROSS_COMPILE_TARGET=yes
export HOSTARCH=ppc-linux
export BUILDARCH=x86_64-linux-gnu
http://randomsplat.com/id5-cross-compiling-python-for-embedded-linux.html
我能交叉编译的Python 2.7.2与上面的配置我的环境脚本,然后尝试构建greenlet模块产量:
$ python ./setup.py build
running build
running build_ext
building 'greenlet' extension
creating build
creating build/temp.linux-x86_64-2.7
/opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-2/powerpc-none-linux-gnuspe/bin/powerpc-none-linux-gnuspe-gcc -I../../../ltib/rootfs/usr/include -L../../../ltib/rootfs/usr/lib -L../../../ltib/rootfs/lib -fPIC -I/usr/include/python2.7 -c greenlet.c -o build/temp.linux-x86_64-2.7/greenlet.o
In file included from /usr/include/python2.7/Python.h:58,
from greenlet.h:8,
from greenlet.c:5:
/usr/include/python2.7/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
error: command '/opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-2/powerpc-none-linux-gnuspe/bin/powerpc-none-linux-gnuspe-gcc' failed with exit status 1
为什么setup.py从我的主机系统上的/usr/include/python2.7
中提取?我无法在我的目标上找到那个目标。我如何为我的目标创建它?
有什么建议吗?
谢谢!
特雷弗
更新#1:
我对目标的根文件系统的我的主机的复制相对引用是不正确的。纠正它并重新运行良率:
$ python ./setup.py build
running build
running build_ext
building 'greenlet' extension
creating build
creating build/temp.linux-x86_64-2.7
/opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-2/powerpc-none-linux-gnuspe/bin/powerpc-none-linux-gnuspe-gcc -save-temps -Wall -I../../ltib/rootfs/usr/include -I../../ltib/rootfs/include/python2.7 -L../../ltib/rootfs/usr/lib -L../../ltib/rootfs/lib -fPIC -I/usr/include/python2.7 -c greenlet.c -o build/temp.linux-x86_64-2.7/greenlet.o
greenlet.s: Assembler messages:
greenlet.s:832: Error: syntax error; found `(' but expected `,'
greenlet.s:832: Error: junk at end of line: `(31),1'
error: command '/opt/freescale/usr/local/gcc-4.3.74-eglibc-2.8.74-dp-2/powerpc-none-linux-gnuspe/bin/powerpc-none-linux-gnuspe-gcc' failed with exit status 1
至少它是找到更多我的目标的包含库,但现在我真的难倒了! :(
任何建议
感谢
更新#2:?!
通过添加-save-temps
标志编译器(上更新错误),我才得以保全,并检查中间的汇编代码在上面的错误信息中提到,虚线包括:
#APP
# 52 "platform/switch_ppc_linux.h" 1
mr 8(31), 1
# 0 "" 2
MR(移动寄存器)op是公平的简单,只接受2个参数(mr to-reg, from-reg
)。我不知道如何添加附加寄存器编号的括号。 FWIW,这里是上述头文件中引用的宏:
#define STACK_REFPLUS 1
#ifdef SLP_EVAL
#define STACK_MAGIC 3
/* !!!!WARNING!!!! need to add "r31" in the next line if this header file
* is meant to be compiled non-dynamically!
*/
#define REGS_TO_SAVE "r13", "r14", "r15", "r16", "r17", "r18", "r19", "r20", \
"r21", "r22", "r23", "r24", "r25", "r26", "r27", "r28", "r29", \
"cr2", "cr3", "cr4"
static int
slp_switch(void)
{
register int *stackref, stsizediff;
__asm__ volatile ("" : : : REGS_TO_SAVE);
__asm__ ("mr %0, 1" : "=g" (stackref) :);
{
SLP_SAVE_STATE(stackref, stsizediff);
__asm__ volatile (
"mr 11, %0\n"
"add 1, 1, 11\n"
"add 30, 30, 11\n"
: /* no outputs */
: "g" (stsizediff)
: "11"
);
SLP_RESTORE_STATE();
}
__asm__ volatile ("" : : : REGS_TO_SAVE);
return 0;
}
#endif
我开始怀疑,如果这是在编译器中的错误,因为宏似乎很简单!有什么建议么? ... 谢谢!
鉴于该博客文章的评论似乎意味着人们甚至没有获得目标Python来导入标准库模块,指令不适用于第三方模块也不足为奇...... – abarnert 2012-07-20 22:26:17
这不是问题所在(标题问题?),我可能会遗漏一些东西,但是您没有指定PPC而不是ARM工具链? – 2012-07-20 22:27:03
@TiloWiklund:很好。他从中复制的博客是关于ARM和PPC的交叉编译,他似乎抄袭了错误的博客。这实际上并不能解释他的问题,因为如果他使用了ARM工具链,情况会完全相同。但这意味着他在尝试为它构建扩展之前,还没有尝试过对其构建的Python进行最低限度的测试。 – abarnert 2012-07-20 22:30:29