Comment # 22 on bug 1179155 from
(In reply to Richard Biener from comment #21)
>    Mesa-drivers
Depends on llvm11 directly now.

>    bcc
Seems to depend on llvm directly, which means it would use llvm7 in SLE/Leap.
Which is probably fine, but BPF is a relatively new target, so an update is
probably not a bad idea.

>    beignet
Builds with llvm7 latest anyway. Strangely Factory has a different specfile
specifically asking for llvm7, but SLE still uses the metapackage. I don't see
a reason to not update though.

>    gnome-builder
>    gnome-code-assistance
These are probably using libclang. I think using a newer version wouldn't hurt.
If we don't, we'll have to live with Leap users having Clang 7 under the hood
as well.

>    libclc
This should probably use the same LLVM version that Mesa is using. The package
consists of LLVM IR files, and while the format is mostly stable I'm not sure
if that's guaranteed. Package is also somewhat outdated... but not sure what
the update policy is here. Though if you update Mesa, then this should be fine
to update as well.

>    meson-testsuite
No idea what the test suite is doing with LLVM, but probably not so important.

>    rust
Interesting case. Rust uses the somewhat unstable LLVM API, which means it
typically needs changes for every new LLVM version. So it should probably not
require the metapackage but something like llvm-devel-provider < (N+1).0.0, or
cmake(LLVM) < (N+1).0.0 where N is the latest supported version.


You are receiving this mail because: