Dear Andrew, I perform "gcc -v", and this is the result: Using built-in specs. Target: arm-eabi Configured with: /home/jingyu/projects/gcc/android-toolchainsrc/build/../gcc/gcc-4.4.3/configure --prefix=/usr/local --target=arm-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/home/jingyu/projects/gcc/toolchain_build/gingerbreadobj/temp-install --with-mpfr=/home/jingyu/projects/gcc/toolchain_build/gingerbreadobj/temp-install --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable-libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --with-float=soft --with-fpu=vfp --with-arch=armv5te --enable-target-optspace --with-abi=aapcs --with-gcc-version=4.4.3 --with-binutils-version=2.19 --with-gmp-version=4.2.4 --with-mpfr-version=2.4.1 --with-gdb-version=7.1.x --with-arch=armv5te --with-multilib-list=mandroid --with-sysroot=/usr/local/google/home/android/cupcake_rel_root --enable-gold=both/gold --program-transform-name='s&^&arm-eabi-&' Thread model: single gcc version 4.4.3 (GCC)
It seems to look for libs via absolute path. Right? Oh, did you mean set this path [LDFLAGS="-Wl,-rpath,$PREFIX/lib"] as relative path ? If so...but i don't know how to set, could you pls kindly help me ? On Thu, May 24, 2012 at 9:56 PM, Andrew Bradford < [email protected]> wrote: > On Thu, 24 May 2012 07:52:51 -0500 > DJ Lucas <[email protected]> wrote: > > > On 05/24/2012 06:36 AM, Andrew Bradford wrote: > > > On Thu, 24 May 2012 13:03:12 +0800lee sudo<[email protected]> > wrote: > > > > > >> But I find some cross toolchains (e.g. cross toolchain in android > source > > >> code) could work well after change its path(anywhere). > > > > git > > clone|https://android.googlesource.com/platform/manifest||for the whole > > schebang, or dig a little deeper for only the toolchain, I believe > > platform/||prebuilt/linux-x86/toolchain/arm-eabi-${GCC_VERSION}||.| > > || > > Thanks! I question Google's need for putting compiled gcc versions in a > git tree, but that's a separate debate :) > > It looks like Google's Android gcc, so long as you move the entire > 'prebuilt/linux-x86/toolchain/$ARCH' directory structure around as one > unit, is using relative paths for their GCC. Their gcc, for example, > looks for libs in '../lib/gcc/$ARCH/$GCC_VERSION', relative to the gcc > binary. > > If you build your GCC like Google does, you should get the same > effect. CLFS doesn't have you do it the Google way, CLFS is more like > how Emdebian's cross compilers are built, with explicit paths to find > libs. I don't know how to tell you how to do it the Google way, but > the GCC manuals should. > > -Andrew > _______________________________________________ > Clfs-dev mailing list > [email protected] > http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org > -- Thanks & BR, sudolee
_______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
