Created attachment 4718 [details] the config file from buildroot Once the disk images have been built and transplanted to the embedded system. The python seems to function correctly, however some python packages require the use of GCC to build the libraries when executing the install of these packages: "python setup.py install" the python setup for GCC points to the OLD location on the computer used to cross build the environment: /home/bob/buildroot-2012.08/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc -fno-strict-aliasing -pipe -Os -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c conftest.c -o conftest.o unable to execute /home/bob/buildroot-2012.08/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc: No such file or directory error: command '/home/bob/buildroot-2012.08/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc' failed with exit status 1 # rather than the new location in the embedded systems 'file system'
Do you intend to install python packages directly from the target into the target? (not from buildroot) The recommended way if you're missing packages is to create new ones in buildroot. And since the toolchain in the target has been deprecated only pure python packages would work your way.
We don't support building things on the target, and the reporter hasn't provided any further input on the issue. Feel free to reopen, and open a different bug, if you're affected by this problem.