From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7124] New: Use BR toolchain externally results a non-bootable root filesystem
Date: Sat, 31 May 2014 13:03:03 +0000 (UTC) [thread overview]
Message-ID: <bug-7124-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7124
Summary: Use BR toolchain externally results a non-bootable
root filesystem
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: xxiao8 at fosiao.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
To reproduce(I used IMX6 board)
1. set HOST_DIR to wherever you want to relocate the toolchain.
2. make toolchain
3. build a rootfs using the above-built toolchain _externally_.
4. boot it up, you will find error saying "no init is found"
To fix it manually we need add a ld-linux.so.3 symlink under /lib on the rootfs
1. cd output/target/lib
2. ln -s ld-linux-armhf.so.3 ld-linux.so.3
3. boot with the modified rootfs
If we use internal buildroot toolchain directly, the ld-linux.so.3 is there. If
we use external buildroot toolchain, the ld-linux.so.3 was not created somehow.
--
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:[~2014-05-31 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 13:03 bugzilla at busybox.net [this message]
2014-05-31 13:06 ` [Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem bugzilla at busybox.net
2014-05-31 13:06 ` bugzilla at busybox.net
2014-05-31 14:09 ` bugzilla at busybox.net
2014-05-31 14:10 ` bugzilla at busybox.net
2014-08-15 17:12 ` 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-7124-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