From: Jay Snyder <jay.snyder@tycoelectronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: several recipes give a link error: libc.so, needed by libgcc_s.so, not found
Date: Mon, 23 Aug 2010 15:16:48 -0400 [thread overview]
Message-ID: <4C72C920.7080709@tycoelectronics.com> (raw)
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
next reply other threads:[~2010-08-23 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 19:16 Jay Snyder [this message]
2010-08-23 20:58 ` several recipes give a link error: libc.so, needed by libgcc_s.so, not found Frans Meulenbroeks
2010-09-21 17:47 ` Johan Hovold
2010-09-21 18:53 ` Roman I Khimov
2010-08-23 21:04 ` Khem Raj
2010-08-23 21:55 ` Maksym Parkachov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C72C920.7080709@tycoelectronics.com \
--to=jay.snyder@tycoelectronics.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.