On 22 August 2011 05:56, Christian Robottom Reis kiko@linaro.org wrote:
On Fri, Aug 19, 2011 at 11:45:47AM -0700, Zach Pfeffer wrote:
On 19 August 2011 09:36, Botao Sun botao.sun@linaro.org wrote:
Currently, we have 2 different situations according to our 2 different tool chains - old and new.
What do old and new mean here?
old: Toolchain targeting generic arm-eabi new: Toolchain targeting arm-linux-androideabi
The difference is that the "old" toolchain doesn't have any understanding of Android internals (stuff like crtbegin.o vs. crt0.o) while the "new" toolchain does -- so "gcc -o busybox *.o" does the right thing with the "new" toolchain, but complains about missing crt0.o and friends with the "old" toolchain.
The fix is to add the -nostdlib /path/to/crtbegin.o /path/to/libc ... mess Android's build system adds everywhere while we're using the arm-eabi-* toolchain.
ttyl bero