Yohan Fernando 
I have successfully compiled the target build for my mini6410. I used Qt4.7.4 and the 4.5.1 toolchain. I copied the libraries, and set the parameters in cd /etc/init.d/rcS and cd /etc/profile I tried running the examples and demos which were built as part of the target build but they did not execute. They came up with some GLIBC error. Thereafter, I installed the SDK, and then used one of the given examples (analogclock) and then re-built it, and compiled it for the target board. I used the "file" command for the executable and it came up with this, analogclock: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.27, not stripped I copied the executable, changed permissions, and when I executed it(via telnet) I got this error, ./analogclock: /lib/libc.so.6: version `GLIBC_2.9' not found (required by /usr/local/qt/lib/libQtGui.so.4) ./analogclock: /lib/libc.so.6: version `GLIBC_2.10' not found (required by /usr/local/qt/lib/libQtNetwork.so.4) ./analogclock: /lib/libc.so.6: version `GLIBC_2.9' not found (required by /usr/local/qt/lib/libQtCore.so.4) This was for both the execution commands "./analogclock -qws" and "./analogclock" One thing I must say is that my board is very similar to the mini6410. It is the idea 6410 and has the exact specs and processor. I was given a toolchain with the board (4.2.2) and it comes up as "arm-unknown-linux-gnueabi" so should I use that toolchain? Or will the toolchain not affect this GLIBC error? How do I fix this?