dpmin7 wrote: @nikic <
I agree that this change needs to be merged into main first before considering any backport, and I understand that older LLVM releases do not accept patches. I have also opened the corresponding pull request against the main branch here: https://github.com/llvm/llvm-project/pull/194511 However, regarding the lib / lib64 distinction, I still think this change is meaningful for multilib build environments. In Yocto 32-bit multilib builds, for example, the library installation path is not always limited to just lib or lib64. Depending on the build configuration, paths such as lib, lib32, lib64, or other custom library suffix paths may be used. In such environments, a shared library built for a 64-bit target is expected to be installed under /usr/lib64, while a 32-bit one may be installed under /usr/lib. (Or conversely, 32-bit libraries may be installed in /usr/lib32 and 64-bit libraries in /usr/lib) With the current default behavior, the runtime library is always installed under /usr/lib, which does not seem appropriate for a multilib build environment where 32-bit and 64-bit libraries need to coexist. I understand that COMPILER_RT_INSTALL_LIBRARY_DIR can be specified directly, but I think it would still be useful for the default behavior to respect the configured library suffix/path in multilib environments. Please let me know if my understanding is incorrect or if there is a better way to handle this case. https://github.com/llvm/llvm-project/pull/194526 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
