Change in glibc 2.31: https://sourceware.org/git/?p=glibc.git;a=commit;h=7bdb921d70bf9f93948e2e311fef9ef439314e41 Clang bug: https://bugs.llvm.org/show_bug.cgi?id=45034 Patch proposed for LLVM: https://reviews.llvm.org/D74712 Example errors during linking: undefined reference to `__log_finite' undefined reference to `__log2_finite' undefined reference to `__log10_finite' undefined reference to `__exp_finite' undefined reference to `__exp2_finite' undefined reference to `__pow_finite'
Fix: "master" branch: https://reviews.llvm.org/rG6d15c4deab51498b70825fb6cefbbfe8f3d9bdcf https://github.com/llvm/llvm-project/commit/6d15c4deab51498b70825fb6cefbbfe8f3d9bdcf "release/10.x" branch: https://reviews.llvm.org/rGcd0926d087a85c5ee1222ca80980b4440214a822 https://github.com/llvm/llvm-project/commit/cd0926d087a85c5ee1222ca80980b4440214a822
OK we should probably wait for llvm-10 release before rekeywording glibc-2.31
This is fixed in llvm-10, which is now in the tree
I think that LLVM maintainers wanted to backport fix to new revision of at least sys-devel/llvm 9.0.1 (and less likely 7.1.0 and 8.0.1).
How does this bug manifest itself? I was able to recompile llvm-9 with glibc-2.31-r6 today.
Created attachment 655054 [details, diff] layman backport from llvm-10.x branch I did a silly little backport myself. I can test it, but need to know how to reproduce first.