Opened 4 years ago
Closed 4 years ago
#14673 closed enhancement (fixed)
llvm-11.1.0
| Reported by: | Douglas R. Reno | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | normal | Milestone: | 10.1 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
New minor version
Change History (5)
comment:1 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 4 years ago
comment:3 by , 4 years ago
Thank you for the heads up on this. I guess we might need to rebuild Mesa/v4l-utils on existing systems, and I guess maybe firefox, ncftp (doubtful on that), dhcpcd (again I doubt this), thunderbird, libreoffice, and seamonkey. I know v4l-utils and Mesa both link to LLVM, but I'm not sure if packages that just use it for compilation are going to be affected.
My current approach for this will be to complete other BLFS tickets first, then LLVM, and then take care of LFS. I'd like to get this done today, but we'll see where I am in ~12 hours :)
comment:4 by , 4 years ago
The ABI breakage is in libclang, not libLLVM. I don't think anything in BLFS (other than clang itself) uses libclang...
I just upgraded LLVM on my system, and it seems mesa and v4l2 are still working perfectly.
According to phoronix, this is to fix ABI breakage in 11.0. Therefore it itself changes the ABI https://bugs.llvm.org/show_bug.cgi?id=46526 - comment 2. Unlikely to be an issue for anyone making a fresh build, but I guess that anyone upgrading from 11.0 or 11.0.1 might need to recompile something.