| Summary: | Use BR toolchain externally results a non-bootable root filesystem | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | xxiao <xxiao8> |
| Component: | Other | Assignee: | Thomas Petazzoni <thomas.petazzoni> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2014.05 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: |
defconfig to build the toolchain
defconfig using the built toolchain as an external toolchain |
||
|
Description
xxiao
2014-05-31 13:03:02 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? Created attachment 5420 [details]
defconfig to build the toolchain
Created attachment 5426 [details]
defconfig using the built toolchain as an external toolchain
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. |