[Buildroot] external buildroot toolchain: LD_LIBRARY_PATH needed

[Grant Edwards <grant.b.edwards@gmail.com>]

On 2011-08-24, Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> 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=<buildroot>/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