Noticed by Whissi: $ scanelf -L -n -q -F '%n #F' /bin/bash libreadline.so.8,libtinfo.so.6,libc.so.6 These should report absolute paths. glibc-2.32 enabled new ld.so.cache format. We'll need to add support for it around https://gitweb.gentoo.org/proj/pax-utils.git/tree/paxldso.c#n179
does this have any real consequences? glibc-2.32-r2 is stable now, can user upgrade or rather wait for pax-utils update?
I'm not aware of any code that uses it for critical purposes.
(In reply to Sergei Trofimovich from comment #2) > I'm not aware of any code that uses it for critical purposes. Yeah, the only issue is for developers. We use it for some of our reverse dependency scripts.
Manually generating the cache with the legacy/compat format works for now: $ ldconfig -c compat $ ~/bin/rdeps.sh /usr/bin/install sys-apps/acl:0: /lib64/libacl.so.1.1.2253 sys-apps/attr:0: /lib64/libattr.so.1.1.2448 sys-libs/glibc:2.2: /lib64/libc-2.32.so