Date: Mon, 08 Aug 2022 17:58:08 +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-XUPJQoxzK0@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 #15 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Brooks Davis from comment #14) Yes, our ports only sporadically use USE_CSTD=3D, and that is a pity since compilers tend to change their defaults every few years while lots of softw= are stays the same. :) That said, it's not always as easy as "just set USE_CSTD=3Dgnu89". For inst= ance, one of the "top 5" ports Antoine mentions in comment 8 is devel/jam, which = is a prehistoric version of boost-build's bjam. This does not respect CFLAGS at = all, so options inserted by USE_CSTD are completely ignored. Also, since it is a build tool, after its bootstrap phase it uses its *own* build logic (i.e. jamfiles), which again have to be patched manually... In any case, it might be possible to grep through the failure logs and iden= tify ports that fail due to K&R prototype warnings, then set those to USE_CSTD= =3Dgnu89 (or some other old version). But you'd still have to attempt to build them before committing. All in all quite a bit of work. --=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-XUPJQoxzK0>