On 12/12/2021 18:57, tastytea wrote:
On 2021-12-12 18:11+0200 Nikos Chantziaras <[email protected]> wrote:
After upgrading from portage 3.0.28 to 3.0.30, I get this when doing
emerge --depclean:
Calculating dependencies... done!
* Broken soname dependencies found:
* x86_64: libexpat.so required by:
* app-emulation/vmware-workstation-16.2.1.18811642-r1
[...]
* x86_64: liblttng-ust.so.0 required by:
* dev-dotnet/dotnet-sdk-bin-6.0.100
[...]
It means the binary wants to load some libraries (like libexpat.so)
portage can't find.
(And before anyone asks, the software works just fine, and neither
revdep-rebuild nor revdep-rebuild.sh find anything wrong.)
But vmware (or rather, the linker) seems to find them. Maybe they are in
the same directory as the binary and portage doesn't search there? You
can check which libraries exactly the binary wants to load with ldd.
Example:
$ ldd
/opt/vmware/lib/vmware-installer/3.0.0/python/lib/lib-dynload/readline.cpython-39-x86_64-linux-gnu.so
ldd: warning: you do not have execution permission for
`/opt/vmware/lib/vmware-installer/3.0.0/python/lib/lib-dynload/readline.cpython-39-x86_64-linux-gnu.so'
linux-vdso.so.1 (0x00007ffde924c000)
libreadline.so.6 => not found
It seems the new portage version does these checks now. Is there a way
to opt-out of those checks?
