Re: SDK problems. GCC won't launch because it can't find libmpfr.so.4

Re: SDK problems. GCC won't launch because it can't find libmpfr.so.4

[Tasslehoff Kjappfot]

  This is apparently because it wants a native version of libmpfr.so.4, 
which is not available for Ubuntu 10.04. OE compiled a version of the 
library in the TMPDIR where I created the SDK, but of course that is not 
distributed with the SDK.

I tried grabbing libmpfr.so.4 from Ubuntu 10.10, but then it complained 
about libgmp.so.10 not being found. Am I doing something very wrong 
compiling the SDK since it creates a GCC that wants libraries not 
present on the system where I created the SDK?

- Tasslehoff

SDK problems. GCC won't launch because it can't find libmpfr.so.4

[Tasslehoff Kjappfot]

  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