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...
Rodney W. Grimes
freebsd at pdx.rh.CN85.dnsmgr.net
Sat Mar 31 14:14:33 UTC 2018
> 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?
>
> 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
> easily.
>
> I am very disappointed in the timing of this change.
Another example of the projects failure to communicate.
This bad timing could of been avoided if a pre commit
email could of been sent out saying that this was about
to be commited.
We need to let each other know -pre- commit if we are
going to do something with wide impact.
I would consider updating any toolchain item in a stable/
branch to be a wide impact.
Further I would support a request to have this
backed out and reapplied at a later date.
Regards,
--
Rod Grimes rgrimes at freebsd.org
More information about the svn-src-stable-11
mailing list