ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltib] Sourcery G++ Lite 2010.09-55 for Power GNU/Linux toolchain


From: Aaron Wegner
Subject: [Ltib] Sourcery G++ Lite 2010.09-55 for Power GNU/Linux toolchain
Date: Thu, 14 Jul 2011 17:50:03 -0400
User-agent: SquirrelMail/1.4.21

I downloaded the latest CodeSourcery G++ Lite toolchain from their site
and popped it into the LPP.

/opt/ltib/pkgs/freescale-powerpc-linux-gnu-2010.09-55.i686.rpm

This RPM works fine with my 32-bit Fedora 12 development workstation.  In
my defconfig.dev I have:

CONFIG_TOOLCHAIN="freescale-powerpc-linux-gnu-2010.09-55.i686.rpm"
CONFIG_TOOLCHAIN_PATH="/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu"
CONFIG_TOOLCHAIN_PREFIX="powerpc-linux-gnu-"
CONFIG_TOOLCHAIN_CFLAGS="-msoft-float -mcpu=860"

However, when I try the same on my 64-bit Fedora 15 development
workstation I find that I'm not able to link.  It bails with linker errors
such as:

----
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/lib/gcc/powerpc-linux-gnu/4.5.1/../../../../powerpc-linux-gnu/bin/ld:
skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/lib/gcc/powerpc-linux-gnu/4.5.1/../../../../powerpc-linux-gnu/bin/ld:
cannot find /lib/libc.so.6
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/lib/gcc/powerpc-linux-gnu/4.5.1/../../../../powerpc-linux-gnu/bin/ld:
cannot find /usr/lib/libc_nonshared.a
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/lib/gcc/powerpc-linux-gnu/4.5.1/../../../../powerpc-linux-gnu/bin/ld:
cannot find /lib/ld.so.1
collect2: ld returned 1 exit status
----

I poked around a little and found that if I edit the gcc spoof source
found in

/opt/ltib/usr/spoof/gcc

and put in the following hack around line 46

#    @srch  = ('-B', "$ENV{DEV_IMAGE}/usr/lib//",
    @srch  = ("-Wl,-L/home/aaron/ltib/rootfs/usr/lib//",

that all my programs compile and link like normal.  Is this a product of
the toolchain?  Is there a workaround that is an easy fix, or is this a
more difficult issue?


Thanks,

Aaron




reply via email to

[Prev in Thread] Current Thread [Next in Thread]