Date: Mon, 04 Mar 2019 18:11:58 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 236062] [exp-run] Against projects/clang800-import branch Message-ID: <bug-236062-7788-BkKo17Swqv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236062-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-236062-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=3D236062 --- Comment #4 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Jan Beich from comment #3) > Can you expedite landing in order to MFC to /stable/11 and /stable/12 > *before* the slush? Sure, I'm fine with that. I requested this exp-run specifically to ensure = that there are no major problems with ports. And indeed, the number of failures seems to be quite low, and most are easy to fix (if a bit cumbersome). > -Werror bustage with few if any blocked ports can be safely ignored for t= he > maintainers are often at fault for keeping the flag by default. In many > cases -Werror is used together with -Wall, -Wextra, -Weverything, etc. wh= ich > practically asks for bustage on compiler upgrade. Yup, let's suppress those warnings, unless they are trivial to fix. > Once FreeBSD 12.0 reaches EOL I'd like to start lifting LLD_UNSAFE. LLD 8 > would help with that e.g., bug 233740 comment 10. >=20 > If C++20 is released during FreeBSD 11.3/12.1 lifetime ports may have > growing pains because libc++ cannot be easily replaced. And USES=3Dcompil= er > better remain nop to avoid exp-run churn. The C++20 support in libc++ 8.0 is obviously not 100% finished either, but = it's pretty OK for at least some time. --=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-236062-7788-BkKo17Swqv>