Thanks for the hint! The static libraries should never be needed at runtime, so what might the reason be to put them in that package? Maybe because they're all coming from compiler-rt? Same goes for the builtin headers. But the remaining files are roughly what I'd imagine. What about the directory? The shared runtime libraries don't live in %{_libdir}, so without RPATH the loader won't find them. If I put them in %{_libdir}, we have problems with multiple versions. And I don't know if the runtimes have ABI stability guarantees, i.e. can you run an application compiled with clang17 with compiler-rt18? Otherwise I might have to add some kind of SO version, something like (lib)compiler-rt%{_sonum}: %{_libdir}/libclang_rt.asan-x86_64.so.%{_soname} clang%{_sonum}: %{_libdir}/clang/%{_sonum}/lib/libclang_rt.asan-x86_64.so -> %{_libdir}/libclang_rt.asan-x86_64.so.%{_soname} What do you think?