You better use Android toolchain to compile qualcomm build. Which tool chain r u using for compiling qualcomm build?
Thanks Gicky On Wed, Nov 12, 2008 at 4:03 PM, <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm using Qualcomm 8250 platform, which comes with a linux kernel > which has android related patches. So I thought everything will be > easy, just put system.img, userdata.img and ramdisk.img to its root > filesystem, then I can try android! > > But things usually not goes that way. I realized that the executables > in system.img and ramdisk.img can't be run under Qualcomm's linux bsp. > > For example, the init in the ramdisk.img, the sh, toolbox in the > system.img /bin directory. Those static linked executable can't be run > under Qualcomm's linux. The result was > > $ ./init > segmentation fault > $ bin/ls > ash: ls not found > > I am wondering why this happened? Is this because the toolchain is > different? Should I use QCOM's toolchain to compile whole android src > tree? > > Regards, > Mac > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
