Date: Thu, 01 Feb 2024 20:21:29 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 276249] lang/python311: Fix armv7 build Message-ID: <bug-276249-21822-EjDBZvG8PL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276249-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-276249-21822@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=3D276249 --- Comment #12 from Benjamin Jacobs <freebsd@dev.thsi.be> --- So llvm17 has been merged to 13-stable and 14-stable, therefore and to my understanding it will likely end up in 13.3 and 14.1 as well. I don't have = the mean to test both 13-stable and 14-stable on my hardware, however it is li= kely that the same problem will occur on those branches, once they are released.= So should we guard against all those versions and keep lto enabled on the still working branches, or simply disable LTO on armv7 overall and leave it like = this until someone tests again on llvm18 once landed ? --=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-276249-21822-EjDBZvG8PL>