On 18/05/2020 13.55, Martin Jansa wrote: > This won't work, because as soon as glibc is upgraded with package > management, the ldconfig files will be restored and there won't be any > do_rootfs hook to remove it. > > Why isn't ldconfig installed in your setup in first place? RRECOMMENDS > should be enough to pull it into every image by default.
[At the risk of sounding like the lady in the Monty Python spam sketch:] I don't _want_ it in my setup - it's a gigantic 700K binary that is useless on a squashfs rootfs where for obvious reasons no new libraries (or new versions) will ever appear. So no, I don't have ldconfig in my distro features (so it's not even rrecommended), and I also don't install recommended packages. I just need a ld.so.cache built at image build time. Which works just fine, except that the drop-in dir gets ignored due to lack of ld.so.conf. After ld.so.cache has been built, the configuration files are welcome to go the way of the dodo. And I'm not removing the ldconfig files if ldconfig is in distro features (or if someone has explicitly RDEPEND'ed on the ldconfig package), so there's no issue of those files getting "restored" - if you have ldconfig on target, they never disappear, so them getting replaced during a package upgrade is not a problem. I'm certainly open to other ways of solving this. But can we agree that it is a bug that the ldconfig done at build-time does not take /etc/ld.so.conf.d/* into account, and that that should not depend on whether one has ldconfig-the-binary on target? Rasmus
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138403): https://lists.openembedded.org/g/openembedded-core/message/138403 Mute This Topic: https://lists.openembedded.org/mt/74289052/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
