[Packaging/LLVM20] libclang-20-dev from apt.llvm.org contains invalid symlink /usr/lib/llvm-20/lib/libclang-cpp.so.20.1

[TheRealCuran]

While trying to build Mesa with LLVM 20 I encountered Mesa bug #11945, which was triggered by libclang-20-dev shipping an invalid Symlink (/usr/lib/llvm-20/lib/libclang-cpp.so.20.1) to a non-existent library (for amd64 eg. ../../x86_64-linux-gnu/libclang-cpp.so.20.1).

The invalid symlink switched the clover build in Mesa over to static linking. Mesa's missing static dependency will be fixed downstream, but it would be nice to be able to build Mesa with a link to clang-cpp.

The symlink should be /usr/lib/llvm-20/lib/libclang-cpp.so.20.0 pointing to ../../${DEB_HOST_MULTIARCH}/libclang-cpp.so.20.0. Please correct the build scripts accordingly.

Please note: this might be a duplicate of #109153 or the two are very likely at least closely related. Since I do install my packages from apt.llvm.org and do not use llvm.sh, I will, however, not make such presumptions. Feel free to merge the tickets, if you believe it is the same.

[doko42]

that should be fixed for the next build of the packages from apt.llvm.org. However I don't know when that happens

[TheRealCuran]

Thank you very much!

For reference: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/032e55dfa39a7a70538db9cb9c591bb88e228cb6 would be the commit, that should fix this issue.

[Zingam]

that should be fixed for the next build of the packages from apt.llvm.org. However I don't know when that happens

Is this bug similar or the same: #109153

Also this one here: #105987

[kimgr]

#109153 is the same, so I think both can be closed.

#105987 is about another solib link, but I believe that's also fixed.

[TheRealCuran]

The issue is closed for me. My latest builds are picking up libclang-cpp.so again. Thanks for the fix @doko42