Bug 709664 – sys-devel/{clang,llvm}-10.0.0_rc2: inconsistent shared library naming & symlinks

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Holger Hoffstätte 2020-02-14 21:23:33 UTC]

I was happy to see that llvm/clang-10 have unified shared libraries, so I
decided to give rc2 a try. Everything builds & works fine, but I noticed inconsistent names & symlinks in /usr/lib/llvm/10/lib64:

llvm has:
lrwxrwxrwx 1   16 Feb 14 14:58 libLLVM-10.0.0git.so -> libLLVM-10git.so
-rwxr-xr-x 1  52M Feb 14 14:58 libLLVM-10git.so
lrwxrwxrwx 1   16 Feb 14 14:58 libLLVM.so -> libLLVM-10git.so

whereas clang has:
lrwxrwxrwx 1   21 Feb 14 15:49 libclang-cpp.so -> libclang-cpp.so.10git
-rwxr-xr-x 1  44M Feb 14 15:49 libclang-cpp.so.10git
lrwxrwxrwx 1   17 Feb 14 15:49 libclang.so -> libclang.so.10git
-rwxr-xr-x 1  35M Feb 14 15:49 libclang.so.10
lrwxrwxrwx 1   14 Feb 14 15:49 libclang.so.10git -> libclang.so.10

I understand the absence of a clear major.minor notation in an rc
(hence the 10git), but IMHO the .so naming and symlink-pointing
should be unified, to be in line with the rest of the system.


Reproducible: Always

Steps to Reproduce:
1. unmask & emerge llvm/clang-10.0.0_rc2
2. see above
3.



It's not clear to me whether this is Gentoo-specific or something worth
reporting upstream. I didn't find anything in upstream's bug tracker,
but that is not surprising given upstream's attitude towards shared libs.
However since it's an rc I figured I report this oddity and see what
other people think.

[Comment 1 Michał Górny 2020-02-15 11:35:15 UTC]

It's an upstream issue and they actually like 'dylibs' (as opposed to split shared).