From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11451] Can't find libmpfr.so.4 when using external toolchain on ubuntu 18.04/18.10
Date: Tue, 30 Oct 2018 08:36:58 +0000 [thread overview]
Message-ID: <bug-11451-163-f3Ol2xaOV9@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11451-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11451
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
If the programs in your external toolchain use libmpfr.so, but it is not
provided by the external toolchain, then the external toolchain is broken.
Your patch causes two problems:
(1) libmpfr.so is not guaranteed to be installed $(HOST_DIR)/lib. Buildroot
only builds/installs host-mpfr if needed, and a typical configuration that uses
an external toolchain will not build/install host-mpfr.
(2) Passing LD_LIBRARY_PATH pointing to some host libraries will very likely
confuse the cross-compilation of some packages. We tried a while ago to use
LD_LIBRARY_PATH, and it was a total failure.
So, here, you really need to fix the external toolchain itself.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-10-30 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 6:37 [Buildroot] [Bug 11451] New: Can't find libmpfr.so.4 when using external toolchain on ubuntu 18.04/18.10 bugzilla at busybox.net
2018-10-30 7:05 ` [Buildroot] [Bug 11451] " bugzilla at busybox.net
2018-10-30 8:36 ` bugzilla at busybox.net [this message]
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=bug-11451-163-f3Ol2xaOV9@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox