llvm-native is pulled into package builds that do not rely on it
Hi,
I am trying to make my meta-clang-revival layer compatible with Yocto 5.3 that merged meta-clang and llvm is split off into its own recipe.
Target recipes that use LLVM 14 or 15 (most notably, variants of intel-compute-runtime and their dependencies) fail with conflicting files being copied into recipe-sysroot-native, like static libs from clang14-native and llvm-native, etc.
As far as I can tell, the issue occurs during packaging, after compilation already succeeded. The dependency chain is correct, otherwise the issue would occur during do_prepare_recipe_sysroot.
It seems that the python function "extend_recipe_sysroot" is re-run for packaging. That's when it fails because llvm-native is pulled in, because llvm-native conflicts with e.g. clang14-native.
Is it because I use signed rpm packaging?
rpm-sequoia-native, while it depends on rust-native, and as a consequence, depends on llvm-native to build, requires neither to run.
How can I avoid this problem without switching to non-signed rpms?
Thanks in advance,
Zoltán Böszörményi