Date: Fri, 08 May 2026 20:54:38 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 290873] devel/libclc: add LLVM 21/22 support Message-ID: <bug-290873-7141-UMbW2SUXBf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290873-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290873 Shawn Webb <shawn.webb@hardenedbsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shawn.webb@hardenedbsd.org --- Comment #5 from Shawn Webb <shawn.webb@hardenedbsd.org> --- I've tried my hand at updating this port, too. I ended up a bit more confused than when I started. It doesn't seem to be written like other ports, doing some weird (rather, "seems weird to me") things. HardenedBSD is actually affected here, since we build base system libraries with LTO. We have to match the default llvm version in ports with what's in base. This is because an older llvm (like what's in ports) cannot read a .a file with LTO-ified objects in it, where those objects were generated with a newer version of llvm (meaning, no forwards compat, which is understandable). llvm was upgraded to 21 in base on 16-CURRENT relatively recently. So folks running an up-to-date HardenedBSD 16-CURRENT won't be able to build devel/libclc, causing a not insignificant cascading failure in ports. I can upload my non-functional patch, but I suspect someone with more experience here could deliver a higher quality than what I can right now. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290873-7141-UMbW2SUXBf>