New comment by kawaiiamber on void-packages repository https://github.com/void-linux/void-packages/pull/27170#issuecomment-749489489 Comment: @q66, without `skiprdeps` on the `musl` arch, `xbps-src` and the checks here report: ```sh => dotnet-sdk-bin-5.0.101_1: running post-install hook: 10-pkglint-devel-paths ... => dotnet-sdk-bin-5.0.101_1: running post-install hook: 11-pkglint-elf-in-usrshare ... => dotnet-sdk-bin-5.0.101_1: running post-install hook: 12-rename-python3-c-bindings ... => dotnet-sdk-bin-5.0.101_1: running post-install hook: 13-pkg-config-clean-xbps-cross-base-ref ... => dotnet-sdk-bin-5.0.101_1: running post-install hook: 99-pkglint-warn-cross-cruft ... => dotnet-sdk-bin-5.0.101_1: running pre-pkg hook: 03-rewrite-python-shebang ... => dotnet-sdk-bin-5.0.101_1: running pre-pkg hook: 04-generate-runtime-deps ... SONAME: libstdc++.so.6 <-> libstdc++>=4.4.0_1 SONAME: libgcc_s.so.1 <-> libgcc>=4.4.0_1 SONAME: libc.musl-x86_64.so.1 <-> UNKNOWN PKG PLEASE FIX! SONAME: libz.so.1 <-> zlib>=1.2.3_1 SONAME: libgssapi_krb5.so.2 <-> mit-krb5-libs>=1.8_1 SONAME: libmscordaccore.so <-> dotnet-sdk-bin (ignored) SONAME: liblttng-ust.so.0 <-> lttng-ust>=2.7.2_1 => ERROR: dotnet-sdk-bin-5.0.101_1: cannot guess required shlibs, aborting! ``` However, on my musl machine, the binaries successfully run and link: ```sh [amber@otaku ~]$ ldd /opt/dotnet/dotnet /lib/ld-musl-x86_64.so.1 (0x7ff2b8419000) libstdc++.so.6 => /lib/libstdc++.so.6 (0x7ff2b816e000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x7ff2b8155000) libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7ff2b8419000) ``` ```sh [amber@otaku ~]$ dotnet --version 5.0.101 ``` Thus, I suspect that it's an internal link in dotnet as you point out.