[oe] several recipes give a link error: libc.so, needed by libgcc_s.so, not found

Johan Hovold johan.hovold at lundinova.se
Tue Sep 21 17:47:26 UTC 2010


On Mon, Aug 23, 2010 at 10:58:07PM +0200, Frans Meulenbroeks wrote:
> 2010/8/23 Jay Snyder <jay.snyder at tycoelectronics.com>:
> > I am getting the following warning (I assume it is a warning, because they
> > all seem to produce working executables) for several recipes (rxvt-unicode
> > shown):
> >
> > ./rxvt-unicode-7.9-r1/temp/log.do_compile.9530:44:/home/oe/build-2010-07-29/tmp/sysroots/x86_64-linux/usr/lib/gcc/i686-angstrom-linux/4.3.3/../../../../i686-angstrom-linux/bin/ld:
> > warning: libc.so, needed by
> > /home/oe/build-2010-07-29/tmp/sysroots/x86_64-linux/usr/lib/gcc/i686-angstrom-linux/4.3.3/../../../../i686-angstrom-linux/lib/libgcc_s.so,
> > not found (try using -rpath or -rpath-link)
[...]
> > There is a file, libc.so in the
> > /home/oe/build-2010-07-29/tmp/sysroots/i686-angstrom-linux/usr/lib path,
> > which IS in an -Wl,rpath= argument being passed to gcc (or g++) (and
> > subsequently to the linker).
> >
> > This problem didn't occur on a git-pull from December 4, 2009, but does on a
> > July 29,2010 pull.
> >
> I have seen the same message for libusb both with gcc 4.4.4 and 4.3.3
> Note that libc.so is in usr/lib while the lib.so.6 file is in lib.
> No idea if that is relevant.
> 
> libc.so contains:
> frans at linux-suse:~/oe/tmp_angstrom/sysroots> cat
> ./armv7a-angstrom-linux-gnueabi/usr/lib/libc.so
> /* GNU ld script
>    Use the shared library, but some functions are only in
>    the static library, so try that secondarily.  */
> OUTPUT_FORMAT(elf32-littlearm)
> GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a  AS_NEEDED (
> /lib/ld-linux.so.3 ) )
> 
> No idea if these should be paths in sysroots (I'm not a dynamic linking expert).

Any progress on this issue?

Meanwhile, adding "-L${STAGING_DIR_TARGET}${base_libdir}" (and perhaps
also a rpath-link directive) to TARGET_LDFLAGS in conf/bitbake.conf
could serve as a work-around.

/Johan




More information about the Openembedded-devel mailing list