Bugzilla – Bug 1090853
duplicate binaries of llvm4 and llvm5
Last modified: 2018-05-18 12:26:55 UTC
llvm4 and llvm5 produce binaries with the same name:
obs cannot handle that properly. Please make sure only one llvm package creates those or include the llvm version in the package name. For now I will disable llvm4 in leap, therefore break klee and creduce.
Only the latest stable llvm version should provide libc++ & libc++abi packages. Since it's always ABI compatible old clang can use them as well.
so maybe a model similar to gcc is needed where the prjconf defines the default version
(In reply to Ismail Donmez from comment #1)
> Only the latest stable llvm version should provide libc++ & libc++abi
> packages. Since it's always ABI compatible old clang can use them as well.
That makes sense.
(In reply to Ludwig Nussel from comment #2)
> so maybe a model similar to gcc is needed where the prjconf defines the
> default version
We have a meta package "llvm" that depends on the default version. But if we have to conditionally disable the build of some subpackages, then I guess a prjconf define would be the way to get it?
yes. meanwhile I've dropped llvm4 and its reverse deps from leap.
I have disabled build of libc++*, python3-clang and libFuzzer packages in all except the last major version that provides them.
*** Bug 1093707 has been marked as a duplicate of this bug. ***