[uClibc] (buildroot) how to install non-pure python modules?

Vladimir Bychkovsky vladimir.bychkovsky at gmail.com
Mon Mar 7 23:33:12 UTC 2005


While trying to add a non-pure python module to a buildroot generated
system I ran into the following problem:

------- The output of installation attempt running directly on the device ----
[root at 192 bsddb3-4.3.0]# python setup.py --berkeley-db=/lib build 
running build
running build_py
running build_ext
building 'bsddb3._pybsddb' extension
/export/home/vladb/svn/buildroot/build_i386/staging_dir/bin/i386-linux-uclibc-gcc
-DNDEBUG -Os -pipe -fPIC -I/lib/include -I/usr/include/python2.3 -c
extsrc/_bsddb.c -o build/temp.linux-i486-2.3/extsrc/_bsddb.o
unable to execute
/export/home/vladb/svn/buildroot/build_i386/staging_dir/bin/i386-linux-uclibc-gcc:
No such file or directory
error: command '/export/home/vladb/svn/buildroot/build_i386/staging_dir/bin/i386-linux-uclibc-gcc'
failed with exit status 1
--------------------------------------

Somehow, python on the target device kept information my cross
compiler (with which python itself had been compiled). Using this
compiler it of course not going to work...

Questions:
1) how to do I reset Pythons information about gcc on the target device?
2) how can I cross-compile a python module?

Thanks,
Vlad.

P.S. ... sigh... now I am going to read about Python Distutils...



More information about the uClibc mailing list