From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] external buildroot toolchain: LD_LIBRARY_PATH needed
Date: Tue, 6 Sep 2011 17:24:25 +0200 [thread overview]
Message-ID: <20110906172425.0fc541eb@skate> (raw)
In-Reply-To: <CAAXf6LUndmNrEU108f1_7h7fC3bsrAAu1Uvf5aOjH+=BJsZCZg@mail.gmail.com>
Hello,
Le Thu, 25 Aug 2011 11:07:31 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> However, the missing library does not seem part of sysroot. It is
> located at output/host/opt/ext-toolchain/lib
> where libgmp, libmpfr, libexpat etc. reside.
Those libraries are libraries for the host, and they are used by gcc
and binutils.
> Maybe this wrapper should be adapted as to include the proper
> LD_LIBRARY_PATH?
No, I don't think it's the right solution. I think there are two
solutions:
* Link the toolchain binaries statically against those libraries so
that the toolchain binaries only rely on the C libraries but not on
gmp, mpfr, etc.
* Link the toolchain binaries with a proper rpath.
> How does crosstool-ng handle this fixed-path problem?
From what I can see, using static linking against those libraries.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-06 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 14:17 [Buildroot] external buildroot toolchain: LD_LIBRARY_PATH needed Thomas De Schampheleire
2011-08-24 14:31 ` Grant Edwards
2011-08-25 9:07 ` Thomas De Schampheleire
2011-09-06 14:17 ` Thomas De Schampheleire
2011-09-06 15:24 ` Thomas Petazzoni [this message]
2011-09-07 10:37 ` Thomas De Schampheleire
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=20110906172425.0fc541eb@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.