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

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

[Jay Snyder]

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)

The following recipes all exhibit this error:

qt4-x11-free-4.6.3-r19.2
gs-8.64-r2
schroedinger-1.0.9-r0
gtk+-2.20.1-r8.1
libsndfile1-1.0.21-r1
mysql-4.1.22-r6
libmusicbrainz-3.0.2-r1
cups-1.4.3-r2
rxvt-unicode-7.9-r1
gnutls-2.8.6-r10.0

Also, anything I attempt to build with the above mentioned qt4-x11-free 
also produce the same warning.

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.

Thanks,
Jay

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

[Frans Meulenbroeks]

2010/8/23 Jay Snyder <jay.snyder@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)
>
> The following recipes all exhibit this error:
>
> qt4-x11-free-4.6.3-r19.2
> gs-8.64-r2
> schroedinger-1.0.9-r0
> gtk+-2.20.1-r8.1
> libsndfile1-1.0.21-r1
> mysql-4.1.22-r6
> libmusicbrainz-3.0.2-r1
> cups-1.4.3-r2
> rxvt-unicode-7.9-r1
> gnutls-2.8.6-r10.0
>
> Also, anything I attempt to build with the above mentioned qt4-x11-free also
> produce the same warning.
>
> 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@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).

Frans

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

[Johan Hovold]

On Mon, Aug 23, 2010 at 10:58:07PM +0200, Frans Meulenbroeks wrote:
> 2010/8/23 Jay Snyder <jay.snyder@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@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

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

[Roman I Khimov]

[-- Attachment #1: Type: Text/Plain, Size: 1131 bytes --]

В сообщении от Вторник 21 сентября 2010 21:47:26 автор Johan Hovold написал:
> On Mon, Aug 23, 2010 at 10:58:07PM +0200, Frans Meulenbroeks wrote:
> > libc.so contains:
> > frans@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.

I have
http://sourceware.org/bugzilla/show_bug.cgi?id=10340
applied locally to binutils, and it works.

-- 
 http://roman.khimov.ru
mailto: roman@khimov.ru
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

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

[Khem Raj]

On Mon, Aug 23, 2010 at 12:16 PM, Jay Snyder
<jay.snyder@tycoelectronics.com> wrote:
> 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)
>
> The following recipes all exhibit this error:

is there a problem you run into because of this warning ?


-Khem

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

[Maksym Parkachov]

Hi Jay,

> ./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)
>

If I remember correctly, you need to put the

TARGET_CC_ARCH += "${LDFLAGS}"

in the offending bb.

Hope this helps,
Maksym Parkachov.