[Webkit-unassigned] [Bug 185194] [GTK] Error building WebKitGtk+ with gcc version 7.3.1

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=185194

--- Comment #14 from Yusuke Suzuki <utatane.tea at gmail.com> ---
(In reply to JF Bastien from comment #13)
> (In reply to Michael Catanzaro from comment #11)
> > I'm having a *lot* of trouble with this. JF, is it OK if I rollout r231170
> > for now? I think we need to; unfortunately, I don't see a path right now to
> > using --std=c++17 with GCC 7.
> 
> I'm fine with it, but it might be better to ask on the thread where we
> agreed to do this migration, with an explanation of what's going on?
> 
> The next step should be this:
>   https://bugs.webkit.org/show_bug.cgi?id=185176
> But I was waiting on hearing from your work to make sure I don't dig a
> bigger hole that we'd need to dig ourselves out of.
> 
> Given the lack of bots, it seems like GCC 7 wasn't an actually supported
> target when we agreed to do this migration. Are you suggesting that GCC 7
> should be officially supported? If so, can we ensure bot coverage of both
> GCC 6 as well as 7 so that breakage can be avoided?

I'm really worried about GCC 7.0's current situation. Next chance we upgrade our compiler is maybe two years later.
If we can upgrade our GCC to 8.0 at that time, it is OK. But if we cannot do that and we need to use GCC 7.0 at that time,
it means we need 4 years to use C++17 from now.

Can we solve the current compile errors by carefully splitting headers, adding includes, etc.? If we can do that, I think we should do.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180508/8925dd4b/attachment.html>