New: Use BR toolchain externally results a non-bootable root filesystem
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.
Signature · 3 lines
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.
[Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem
https://bugs.busybox.net/show_bug.cgi?id=7124
--- Comment #1 from Thomas Petazzoni <[email protected]> 2014-05-31 13:06:29 UTC --- Thanks for your bug report!
Could you provide the .config you have used to build the toolchain, and then the .config you have used to build the root file system?
Signature · 3 lines
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.
[Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7124
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at buildroot.uclibc |thomas.petazzoni at free-elect
|.org |rons.com
Signature · 3 lines
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.
[Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7124
--- Comment #2 from xxiao <[email protected]> 2014-05-31 14:09:33 UTC --- Created attachment 5420
--> https://bugs.busybox.net/attachment.cgi?id=5420
defconfig to build the toolchain
Signature · 3 lines
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.
[Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7124
--- Comment #3 from xxiao <[email protected]> 2014-05-31 14:10:20 UTC --- Created attachment 5426
--> https://bugs.busybox.net/attachment.cgi?id=5426
defconfig using the built toolchain as an external toolchain
Signature · 3 lines
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.
[Buildroot] [Bug 7124] Use BR toolchain externally results a non-bootable root filesystem
In reply to bugzilla at busybox.nethttps://bugs.busybox.net/show_bug.cgi?id=7124
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME--- Comment #4 from Thomas Petazzoni <[email protected]> 2014-08-15 17:12:45 UTC --- I've just tested your use case, and it works fine here. Moreover, from your description, I believe a mistake was done on your side: when you use EABIhf, ld-linux.so.3 should *NOT* be present, and all executables should have /lib/ld-linux-armhf.so.3 as their program interpreter (see the output of
"readelf -a").
Therefore, this makes me believe that you had some non-EABIhf binaries lying around, and they were still referencing /lib/ld-linux.so.3, which on purpose doesn't exist on EABIhf systems.
Consequently, I'm marking this bug as "works for me". Do not hesitate to reopen if you disagree with this conclusion.
Signature · 3 lines
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.