Date: Wed, 05 May 2021 14:06:02 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 255359] www/firefox: Fails to build with LTO enabled after recent update: LLVM ERROR: Broken module found Message-ID: <bug-255359-21738-lf6wgq2K3u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255359-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-255359-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255359 --- Comment #10 from Evgeniy Khramtsov <evgeniy@khramtsov.org> --- (In reply to Dimitry Andric from comment #9) I don't feel like hijacking the topic of this bug for discussion of x11@ policy, but I think I should clarify: > if mesa can compile Upstream accepts LLVM versions >=3D 8.0.0 https://gitlab.freedesktop.org/mesa/mesa/-/blob/mesa-20.2.3/meson.build#L14= 49-1455 For example, Arch Linux already builds against LLVM 11 (see llvm-libs versi= on): https://archlinux.org/packages/extra/x86_64/mesa/ The current LLVM 10 for mesa-libs is outdated. > Note that it says "=3D" not "?=3D" which must be for a reason. :) x11@ favors apparent stability and the use of binary packages. They also think that putting artificial limitations like non-overridable LL= VM version for people who build from source is a good idea, maybe because hand= ling possible reports is too hard. Not to mention the time and carbon footprint = of the hardcoded LLVM version. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255359-21738-lf6wgq2K3u>