I think this has something to do with BusyBox being dependent on libc, which Android's toolchain doesn't have.
On Mar 15, 6:31 am, squix <dani.eichh...@squix.ch> wrote: > I case a static build of busybox is good enough for you, you can > follow this > tutorial:http://wiki.androidx86.org/index.php?title=Installing_BusyBox > With the tool chain questions I can't help you... > > Dani > > On Mar 14, 7:11 pm, "neilnguyen_2...@yahoo.com" > > <neilnguyen_2...@yahoo.com> wrote: > > Dear all: > > > I am a newbie in the Kernel land. I would like to use the prebuilt > > toolchain included in the Android release to build BUSYBOX. I have > > lots of compilation error, and I need help. > > > I understand that I could use CodeSourcery toolchain to build the > > busybox, and create a rootfs for the kernel. > > > Do you think it makes sense to carry two different tool sets, and > > switch it back and forward during the development? > > Also, is it safe to do this if a new toolchain is being released? > > > I am a bit confused, and need help badly. > > Neil > > > My target: > > TARGET=ARM926EJ > > Host=Linux Centos5 --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---