On Tue, Mar 29, 2016 at 11:12 PM, $rik@nth <srikanth0...@gmail.com> wrote: > Yes. I am using ubuntu 64bit to cross compile GCC to ARM. If i issue > --host=arm-linux-gnueabi then it will pick up default > /usr/arm-linux-gnuebi bins. I would like to pick up my binutils which > are built statically for doing some experiment.
If binutils was built and installed with the same prefix as gcc, then gcc should automatically find and use it. For cross building a native, you need to build a cross compiler first, and then put it on your path, in which case the cross built native should use your cross compiler. > --host=arm-linux-gnueabi --target=arm-linux-gnueabi You have host and target, but not build. You should specify all three. > AR=arm-linux-gnueabi-ar CC=arm-linux-gnueabi-gcc > RANLIB=arm-linux-gnueabi-gcc-ranlib-4.7 STRIP=arm-linux-gnueabi-strip > CPP=arm-linux-gnueabi-g++ CXX=arm-linux-gnueabi-g++ You shouldn't have to specify stuff like this. These variables should be set automatically. > Now i am hitting one more issue before earlier one comes. > configure: error: cannot compute suffix of object files: cannot compile > See `config.log' for more details. > make[1]: *** [configure-build-libiberty] Error 1 You have to look at the config.log file to see what command failed. There is more than one config.log file. This would be the file build-$build/libiberty/config.log. This problem might be due to the missing --build configure option. if $build isn't x86_64-pc-linux-gnu or whatever your build machine is, then that is probably why the configure in this directory failed. Jim _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
