Date: Mon, 17 Oct 2022 18:46:33 +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-2Of0eSDTW1@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 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |267156 --- Comment #20 from Dimitry Andric <dim@FreeBSD.org> --- Submitted bug 267156 for databases/db5. In the mean time, I have imported clang 15.0.3 (aka llvmorg-15.0.2-10-gf3c5289e7846) into https://github.com/DimitryAndric/freebsd-src/tree/llvm-15-update. For the llvm-project 15.x branch, upstream has decided to roll back the warning-as-error behavior for -Wimplicit-int and -Wimplicit-function-declaration, in https://github.com/llvm/llvm-project/commit/c0141f3c300fbc002cf79404fa0b82b= 4cb1191df, after the discussion at https://discourse.llvm.org/t/configure-script-breakage-with-the-new-werror-= implicit-function-declaration/65213 . That means that quite a lot (maybe most) of the failures reported in previo= us comments should no longer occur, because these were due to these warnings having been upgraded to errors for clang 15.0.0. (Although there is still a lot of work to be done, if at some point clang 16 should be imported, it se= ems that upstream really wants to re-enable those errors for it.) After the above fix for db5 is committed, I expect that a new run can be do= ne. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267156 [Bug 267156] databases/db5: fix build with clang 15 --=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-2Of0eSDTW1>