From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6452] New: eglibc from Linaro 2013.07 not copied to target correctly
Date: Wed, 14 Aug 2013 05:11:17 +0000 (UTC) [thread overview]
Message-ID: <bug-6452-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6452
Summary: eglibc from Linaro 2013.07 not copied to target
correctly
Product: buildroot
Version: 2013.05
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: henry at echelon.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5042
--> https://bugs.busybox.net/attachment.cgi?id=5042
Preserve toolchain sysroot lib's directory structure on target
When building buildroot with Linaro 2013.07 (configured as external or custom
tool), the target would fail to come up, with error:
/sbin/init: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
The reason is that starting with Linaro 2013.07, they switched to eglibc-2.17
with multi-arch support. Arch-specific libraries, including libc.so.6, are
expected to be in /lib/arm-linux-gnueabihf/ instead of just /lib. However,
copy_toolchain_lib_root() in helper.mk would end up copying them to /lib rather
than arch-specific directories.
Attached is my own patch to preserve the toolchain sysroot's lib directory
structure, except for SUPPORT_LIB_DIR which are still copied directly under
DESTDIR.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-08-14 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 5:11 bugzilla at busybox.net [this message]
2013-10-02 13:20 ` [Buildroot] [Bug 6452] eglibc from Linaro 2013.07 not copied to target correctly bugzilla at busybox.net
2013-10-06 14:32 ` bugzilla at busybox.net
2013-10-30 21:54 ` bugzilla at busybox.net
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-6452-163@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