Date: Mon, 08 Aug 2022 17:49:04 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 265425] [exp-run] Against llvm-15-update branch on GitHub Message-ID: <bug-265425-7788-UWGRrLMT2v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265425-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-265425-7788@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=3D265425 --- Comment #14 from Brooks Davis <brooks@FreeBSD.org> --- Reverting on a temporary basis sounds like it may be the right short-term solution, but it's clearly not a sustainable option. Delaying until (for example) LLVM 16 would let upstreams and some linux distros do some of the = work for us, but I don't really know how much that will help. If we do to the reverting-to-warning route, it would be good to provide a fairly reliable path for people to re-enable the errors (I'll have an llvm15 port later this week) and to notify maintainers of broken port so we can sp= read out the work. Throwing out another idea: would be be possible to more or less automatical= ly test which ports are fixed by USE_CSTD=3Dgnu89? IMO, splatting those in pre= tty indiscriminately would be fine for ports of software written to 23+ year old standards. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265425-7788-UWGRrLMT2v>