From: Jeremy Williams <jerm7861@yahoo.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: nof/libgcc_s.so installed instead of libgcc_s.so on powerpc
Date: Wed, 2 Dec 2009 18:04:21 +0000 (UTC) [thread overview]
Message-ID: <loom.20091202T190012-888@post.gmane.org> (raw)
In-Reply-To: 19c1b8a90911301045i6934e415h9e2adb0f0f3ae82f@mail.gmail.com
Khem Raj <raj.khem <at> gmail.com> writes:
>
> could be that its from one of intermediate gcc stages.
>
libgcc_s.so.1 is provided by both the host package gcc-cross-sdk and the target
package libgcc1, both installed to the same place.
[root@msvm1 powerpc-angstrom-linux]# opkg files gcc-cross-sdk | grep libgcc
/usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so
/usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/nof/libgcc_s.so.1
/usr/local/angstrom/powerpc/lib/gcc/powerpc-angstrom-linux/4.3.3/libgcc.a
/usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so.1
/usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/nof/libgcc_s.so
/usr/local/angstrom/powerpc/lib/gcc/powerpc-angstrom-linux/4.3.3/libgcc_eh.a
[root@msvm1 powerpc-angstrom-linux]# opkg-target files libgcc1
Package libgcc1 (4.3.3-r7.1.4) is installed on root and has the following files:
/usr/local/angstrom/powerpc/powerpc-angstrom-linux/lib/libgcc_s.so.1
Since the files in the image directory of gcc-cross-sdk are correct, I suspect
that it is the fault of libgcc1. I am looking into this further today...after I
get past the latest meta-toolchain build issue... :)
-jeremy
prev parent reply other threads:[~2009-12-02 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 14:34 nof/libgcc_s.so installed instead of libgcc_s.so on powerpc Matteo Fortini
2009-06-15 15:03 ` Leon Woestenberg
2009-06-15 15:21 ` Matteo Fortini
2009-06-18 6:09 ` Khem Raj
2009-06-18 15:17 ` Matteo Fortini
2009-06-27 0:59 ` Khem Raj
2009-11-30 1:15 ` Jeremy Williams
2009-11-30 18:45 ` Khem Raj
2009-12-02 18:04 ` Jeremy Williams [this message]
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=loom.20091202T190012-888@post.gmane.org \
--to=jerm7861@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox