Summary: | www-client/chromium-38.0.2107.2 fails to compile with gcc-4.7 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric Bueschel <ericb> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | alex_y_xu, michal.spondr, norman.shulman |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build Log |
Description
Eric Bueschel
2014-07-31 12:26:54 UTC
Please attach the entire build.log. Created attachment 381942 [details]
Build Log
I think it's related to this change, https://groups.google.com/a/chromium.org/forum/#!topic/chromium-reviews/aVGr3gb-uUk and https://codereview.chromium.org/385743002/ You probably need to upgrade to gcc-4.8. http://thread.gmane.org/gmane.linux.gentoo.devel/92113 just encountered the same error with gcc 4.7.4 not exactly related to this issue but to spare users from re-building chromium *again* when facing this problem: please bump it to 38.0.2107.3 https://code.google.com/p/chromium/issues/detail?id=398751 (In reply to Matt from comment #5) > but to spare users from re-building chromium *again* when facing this > problem: It's masked for a reason. If you are worried about rebuilds, use the stable channel (chromium-36). I acknowledge the issue, and we'll see how the situation develops - whether we can get gcc-4.8 into stable or need to come up with some patches to the sources (which may or may not be feasible depending on further upstream actions). For now stable is not affected and chromium-38 is hard masked, so it's assumed people trying to use it can face issues like this. Please consider using e.g. newer gcc. Upgraded to gcc-4.8.3. Recompiled chromium-38 sucessfully. Confirmed issue and solution. Thank you. *** Bug 521534 has been marked as a duplicate of this bug. *** Per arch testing on bug 524764, this seems to have been resolved upstream. (In reply to Mike Gilbert from comment #10) > Per arch testing on bug 524764, this seems to have been resolved upstream. FWIW we have a patch for that in Gentoo. It's small for chromium-38, but I'd expect this to get harder with more recent versions. |