From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards Date: Wed, 24 Aug 2011 14:31:11 +0000 (UTC) Subject: [Buildroot] external buildroot toolchain: LD_LIBRARY_PATH needed References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 2011-08-24, Thomas De Schampheleire wrote: > If I build a buildroot toolchain on machine A, package the > output/host/usr directory and use that as an external toolchain on > machine B, I get errors that cc1 cannot find libmpfr.so.4. The > location of that library is hardcoded in some compiler tools, and > since we are on another machine, the original location does not > exist. > > I can work around this by specifying > LD_LIBRARY_PATH=/output/host/opt/ext-toolchain/lib in the > environment, but this is an annoying and not so clean solution. > > How is this supposed to work? Generally, when you run a gcc from somewhere othern than the location for which it was originally compled you use the --sysroot option on the compiler command line to tell it where it's now installed. I don't know if the buildroot toolchain has that enabled or not. I had a lot of problems trying to use a buildroot-generated toolchain as an external toolchain (this was a year or two back) and switched to using crosstool-ng to build my toolchains. -- Grant Edwards grant.b.edwards Yow! I wonder if there's at anything GOOD on tonight? gmail.com