Actually it's from http://www.codesourcery.com/, QCOM is using version 2006q3-27.Which's config.. ------------------------ [EMAIL PROTECTED]:~/QCOM/tools/arm-2006q3/bin$ ./arm-none-linux-gnueabi-gcc -v Using built-in specs. Target: arm-none-linux-gnueabi Configured with: /scratch/paul/arm/src/gcc-2006q3/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-shared --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --prefix=/opt/codesourcery --enable-languages=c,c++ --enable-symvers=gnu --enable-__cxa_atexit --with-versuffix='CodeSourcery ARM Sourcery G++ 2006q3-26' --with-pkgversion='CodeSourcery ARM Sourcery G++ 2006q3-26' --with-bugurl=mailto:[EMAIL PROTECTED] --disable-nls --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/paul/arm/install/arm-none-linux-gnueabi/libc Thread model: posix gcc version 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26) ------------------------
Although the gcc version is older than Android toolchain, it generates armv6 code instead of armv5 generated by android toolchain. Did android's toolchain be modified somewhere so you suggest to use this one? Thanks, Mac 2008/11/12 kernel gick <[EMAIL PROTECTED]> > 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 -~----------~----~----~----~------~----~------~--~---
