From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: SDK problems. GCC won't launch because it can't find libmpfr.so.4
Date: Tue, 10 Aug 2010 09:32:45 +0200 [thread overview]
Message-ID: <4C61009D.8050703@gmail.com> (raw)
I've compiled an SDK from a source tree in
//data/src/lead-dev/openembedded/, and the resulting gcc compiler for
arm has an RPATH of
//data/src/lead-dev/openembedded/build/angstrom-dev/sysroots/i686-linux/usr/lib/,
and will only run on my machine as long as that directory exists. If I
remove that directory, it complains about libmpfr.so.4 not being found.
The previous SDK I built also had this odd RPATH, but gcc would run on
other systems even if the RPATH-directory didn't exist.
I have placed the toolchain in a custom location and compile small
applications with makefiles pointing to it. I tried unpacking to
/usr/local/angstrom instead and ran the environment setup script, but
got the same error.
- Tasslehoff
next reply other threads:[~2010-08-10 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 7:32 Tasslehoff Kjappfot [this message]
[not found] <mailman.497.1281430979.3621.openembedded-devel@lists.openembedded.org>
2010-08-10 9:27 ` SDK problems. GCC won't launch because it can't find libmpfr.so.4 Tasslehoff Kjappfot
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=4C61009D.8050703@gmail.com \
--to=tasskjapp@gmail.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.