dvrogozh wrote: Different distros seem to use different approaches to handle `LLVM_ENABLE_PER_TARGET_RUNTIME_DIR` as some (like Debian) has its own policies around multi-arch directories. In particular: * Fedora family builds LLVM with the default `LLVM_ENABLE_PER_TARGET_RUNTIME_DIR=ON` and uses `/etc/ld.so.conf.d/` to add paths to the LLVM directories with triples. See https://src.fedoraproject.org/rpms/llvm/blob/f44/f/llvm.spec#_2046 * Debian family builds with `LLVM_ENABLE_PER_TARGET_RUNTIME_DIR=OFF`. See: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/22/debian/rules?ref_type=heads#L136
Other distros like Arch or Yocto might be doing something differently, but they indeed are aware of the LLVM per target runtime directories approach and handle that. Eventually from above it's important to support both `LLVM_ENABLE_PER_TARGET_RUNTIME_DIR=ON` and `=OFF`. https://github.com/llvm/llvm-project/pull/188770 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
