[REQ] Delete `ld.so.cache` in containers and dynamic linking woes

[Stevenjin8]

What kind of request is this?

None

What is your request or suggestion?

Right now, *.so files are places under /usr/lib/. This is not ideal because AFAIK, ld will not look there by default. It will only look under /usr/lib and /lib and /usr/local/lib. We can modify this behavior, by adding a config file into /etc/ld.so.conf.d/ containing

/usr/lib/<package>

so that ld looks in the right place (TBH, we should probably do this automatically if a spec contains libraries).
Despite this, the ld still doesn't find shared objects in /usr/lib/<package> because its cache ld.so.cache does not get updated/refreshed after updating the config.

The only way around this (AFAIK) is to create a bunch of symlinks under /usr/lib pointing to the files in /usr/lib/<package>

Are you willing to submit PRs to contribute to this feature request?

• Yes, I am willing to implement it.

[cpuguy83]

We discussed changing the implementation to by default put things directly into /usr/lib rather than /usr/lib/<package> and include a subpath where someone can get the old behavior.

I will say most things I've seen seem to put things into a subpath, though.
Typically to link to these you'd use pkg-config to link to them properly.

[krinkinmu]

pkg-config allows us to link against an already installed shared library, but, from what I know, it has no influence on the dynamic linker. If dynamic linker does not know where to find the library, pkg-config will not help, right?

I don't think that there is a workaround that would allow us to install shared libraries into a subdirectory of /usr/lib in a way that works without providing a dynamic linker config and running ldconfig after that.

If DALEC wants to put things into a subdirectory of /usr/lib, then it has to install the libraries differently from what it currently does, because the current way just does not seem to work.

[cpuguy83]

#564