Am 25.06.2018 22:40, schrieb Eli Schwartz: > On 06/25/2018 04:30 PM, Michael D. Setzer II wrote: >> Thanks for all the quick reponses. Tried the options, but am just seeing a >> link >> to libc.so.6 and no other libraries?? > > So your busybox binary is not statically linked. That doesn't really > change anything. > > If your project depends on GNU libc, you are not permitted to "clean up > unused libraries" from glibc, at least not the libnss_* ones, because > GNU libc requires them even though it does not link to them, and it will > use them behind your back *anyway* via dlopen(3) > http://man7.org/linux/man-pages/man3/dlopen.3.html
there is no static version of gnu-libc. But i agree there is other to really know what is needed. Dynamic libraries by there very name are dynamic and may link other libraies in without notice, i doubt ldd will be clever enought to see this. In the give case ldd may be ok, but it is clearly not fool-proof and a runtime test is always required. just my 2 cents, re, wh > > You may solve this by not using GNU libc, or by specifically excluding > these shared libraries from being cleaned, or by writing a build system > which more accurately tracks what libraries to install in the first > place rather than cleaning up after the fact. > > > > > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
