| Summary: | eglibc doesn't install ldconfig to target | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Ryan Coe <bluemrp9> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2013.05 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | install ldconfig to target | ||
ldconfig, nor ldd, are required components on the target system. These are not installed by default, even when using an external toolchain. ldconfig basically updates /etc/ld.so.conf, which can be done by hand. ldd just runs the executable with the env variable LD_TRACE_LOADED_OBJECTS=1 set, so you can obtain the same behavior with: LD_TRACE_LOADED_OBJECTS=1 /usr/bin/foo So I indeed don't think this is a bug. What do other developers think? I agree that this is not a bug: there is no point in having ldconfig installed to the target, since we don't support doing development on target. Therefore, the ld.so.cache should be generated at build time, on the build machine. That said, I believe there is a ldconfig problem: if none was found in the cross-compilation toolchain, we use the one from the build machine, which is wrong. But this is not per-se related to this bug. I do agree that they aren't normally needed on the target filesystem. I am marking this bug as invalid. |
Created attachment 5030 [details] install ldconfig to target I am not 100% sure this is a bug. I noticed that when using the new experimental eglibc package, ldconfig does not get installed to the target. Attached is a patch. I'm also not sure if anything else needs installed as well (like ldd).