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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 8 06:59:11 PDT 2018


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

--- Comment #16 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to JF Bastien from comment #13)
> 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.

Thanks for waiting until we get this resolved.

We also have a problem with clang in bug #185198, but of course that one is related to std::optional too.

> 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?

We definitely need to support both GCC 7 and GCC 8. I'll ask Carlos Lopez if bot coverage would be possible here.

(In reply to Yusuke Suzuki from comment #14)
> 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.

My expectation is this:

 * Debian 10 releases with GCC 8 sometime in 2019. At this point, we'll drop GCC 6 and can require GCC 7.
 * Ubuntu 20.04 releases with GCC 9 in April 2020. At this point, we'll drop GCC 7 and can require GCC 8.

It seems like a reasonable schedule.

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

I failed at that.

(In reply to Yusuke Suzuki from comment #15)
> Another solution is, moving the current our std::optional to WTF::optional.
> And use it. And in some ports, we can use official std::optional.

We should try this. It would be a big patch, but I think it should work.

-- 
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/240c6650/attachment.html>


More information about the webkit-unassigned mailing list