Our chip provider give us a SDK to build arm software. This SDK includes a tow toolchain:arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu and gcc-4.2.4-glibc-2.7-toolchain. They said arm-2009q3 should used to build rootfs and ONLY glibc toolchain can be used to build stage1(boot before u-boot).
According document I uncompress gcc-4.2.4-glibc-2.7-toolchain and add arm-none-linux-gnueabi-xx into PATH environment. But when I call make the following error message prompted:
"
arm-none-linux-gnueabi-as -mapcs-32 -g src/start.S -o obj/start.o
arm-none-linux-gnueabi-as: error while loading shared libraries: libopcodes-2.19.1.20090309.so: cannot open shared object file: No such file or directory
"
I tried the following step to resolve this problem:
1) search libopcodes-2.19.1.20090309.so in toolchain folder. I find two files in different folder:
../gcc-4.2.4-glibc-2.7-toolchain/cross-tools/i386-cross-linux-gnu/arm-unknown-linux-gnueabi/lib/libopcodes-2.19.1.20090309.so
../gcc-4.2.4-glibc-2.7-toolchain/native-tools/usr/lib/libopcodes-2.19.1.20090309.so
2) I add these path into PATH separatly, but none of them tack effect.
3) Then I new a file in /etc/ld.so.conf.d/xxx.conf and add fullpath of "gcc-4.2.4-glibc-2.7-toolchain/cross-tools/i386-cross-linux-gnu/arm-unknown-linux-gnueabi/lib/" in it.
4) call ldconfig
5) aha. now successfully. My OS is Fedora 13.
阅读(1788) | 评论(0) | 转发(0) |
