Date: Wed, 31 Jan 2024 13:42:24 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 276104] [exp-run] Against llvm-18-update branch on GitHub Message-ID: <bug-276104-7788-h6uFA8qnWx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276104-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-276104-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=3D276104 --- Comment #11 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Antoine Brodin from comment #10) Ah sorry about that, I still had one commit in my local repository which I forgot to push to GitHub: https://github.com/DimitryAndric/freebsd-src/commit/17a31069a5f1f8c14c96aa8= 4d874376172ea44a1 This the cause for the "error: chosen constructor is explicit in copy-initialization" messages gotten while compiling most of the llvm ports, and the same code that lives in the rust port. It was an upstream refactori= ng in clang which had to be reverted before 18.0 is released, as it was causing this error even with valid code. I have verified that with 17a31069a5f1f8c14c96aa84d874376172ea44a1, at least llvm12, llvm15 and rust build, and I expect the other llvms to also build. --=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-276104-7788-h6uFA8qnWx>