On Sat, 2010-03-13 at 22:22 -0500, Pawel Pastuszak wrote: > Hi All, > > I am trying to split the toolchain out of my main openwrt build, after > generating the toolchain i moved it to a new location from > staging_dir/toolchain-powerpc_gcc-4.3.3_glibc-2.7 and set up and new > build that points to the toolchain. > > I am using Revision: 20023. > > Is there any think that I am missing? > > > powerpc-openwrt-linux-gnu-gcc -Os -pipe -funit-at-a-time -mcpu=405 > -msoft-float -Wall -Wunused -I./include/linux/include/ -Iinclude/ > -DARPTABLES_VERSION=\"0.0.3-3\" -o arptables arptables-standalone.o > arptables.o libarptc/libarptc.o extensions/arpt_standard.o > extensions/arpt_mangle.o > /development/external_toolchain_test/usr/bin/../lib/gcc/powerpc-openwrt-linux-gnu/4.3.3/../../../../powerpc-openwrt-linux-gnu/bin/ld: > cannot find -lgcc_s > collect2: ld returned 1 exit status > make[4]: *** [arptables] Error 1 > make[4]: Leaving directory > `/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptables-v0.0.3-3' > make[3]: *** > [/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptables-v0.0.3-3/.built] > Error 2 > make[3]: Leaving directory `/development/openwrt/package/arptables' > make[2]: *** [package/arptables/compile] Error 2 > make[2]: Leaving directory `/development/openwrt' > >
Looks like a relocation problem. In general, gcc has a hard coded absolute path to some libraries. Solution is to compile the cross compiler for your new destination path or fix the binary. This has been discussed quite recently here in the "Compiling outside of buildroot" thread. Bas. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
