svn commit: r331838 - in stable/11: . contrib/compiler-rt/include/sanitizer contrib/compiler-rt/include/xray contrib/compiler-rt/lib/BlocksRuntime contrib/compiler-rt/lib/asan contrib/compiler-rt/l...
dim at FreeBSD.org
Sat Mar 31 16:44:10 UTC 2018
On 31 Mar 2018, at 15:18, Mark Linimon <linimon at lonesome.com> wrote:
> On Sat, Mar 31, 2018 at 02:42:01PM +0200, Dimitry Andric wrote:
>> It's been almost 3 months now since clang 6 landed in head, and if
>> those ports require USE_CXXSTD=gnu++98 to be fixed, why haven't those
>> already been changed already?
> Because it takes a lot of time and effort to do it?
I don't want to belittle anyone's work here, but I am very disappointed
that it apparently takes more than 3 months (half the lifecycle of a
complete upstream llvm release!) to fix broken ports. Don't maintainers
read their email, or care about their ports?
> This basically torpedoes the work I've been trying to do to catch tier-2
> up to tier-1, on 11. I had been trying to to identify all the problems
> that existed beforehand, before starting in on the clang6 ones. (Many
> people have also been contributing to fixing clang6/amd64/current errors,
> and I wanted to let the work settle, and not duplicate.)
> Finally, if this had gone in just two days later, it would not have
> affected the Q2 package builds. I could have lived with that a lot more
> I am very disappointed in the timing of this change.
In fact, I thought this was the perfect timing, so that the quarterlies
are built with clang 6, and it has enough time to settle for the 11.2
slush. If this was merged later, somebody else would probably have
grumbled that I had "merged it just before slush". :)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 223 bytes
Desc: Message signed with OpenPGP
More information about the svn-src-stable-11