Summary: | www-client/chromium is not gcc-4.7 compatible | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | iGentoo <AlphatPC> |
Component: | [OLD] Unspecified | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | biert85, dev-zero, facorread, jauhien, jcallen, jlec, kuba.iluvatar, marduk, Martin.Jansa, patrizio.bassi, shubhadeepc, tdalman |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
http://code.google.com/p/chromium/issues/detail?id=120724 http://code.google.com/p/chromium/issues/detail?id=122525 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 427246 | ||
Bug Blocks: | 390247 | ||
Attachments: |
build.log.tar.xz
gcc-4.7.patch Patch from upstream chromium-gcc-4.7-r1.patch |
Description
iGentoo
2012-04-19 08:30:14 UTC
Created attachment 309497 [details]
build.log.tar.xz
Created attachment 309499 [details, diff]
gcc-4.7.patch
I'll reply in the upstream bug. (In reply to comment #3) > I'll reply in the upstream bug. Even if you're going to do all the work upstream, this bug is still needed open as it tracks the issue in Gentoo giving the porting team valuable information about affected versions in tree. The best way to close it later on, is to paste relevant part of ChangeLog or at least the info in which version it was fixed. Also note a segmentation fault that happens after successful compilation. Same problem for me. The patch fails when applying to www-client/chromium-20.0.1132.17 *** Bug 417389 has been marked as a duplicate of this bug. *** (In reply to comment #7) > The patch fails when applying to www-client/chromium-20.0.1132.17 Same here Same error with chromium-21.0.1145.0 Alright so taking the patches included in the AUR package from Arch: https://aur.archlinux.org/packages.php?ID=37244 gcc47v3.diff ipc-fix.diff sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch and applying them to 21.0.1145.0 makes it compile with gcc-4.7 and fixes (I haven't experienced any segfaults so far) the segfaults. (In reply to comment #11) > Alright so taking the patches included in the AUR package from Arch: > https://aur.archlinux.org/packages.php?ID=37244 > > gcc47v3.diff > ipc-fix.diff > sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch > > and applying them to 21.0.1145.0 makes it compile with gcc-4.7 and fixes (I > haven't experienced any segfaults so far) the segfaults. For worked. Thanks (In reply to comment #11) > Alright so taking the patches included in the AUR package from Arch: > https://aur.archlinux.org/packages.php?ID=37244 > > gcc47v3.diff > ipc-fix.diff > sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch > > and applying them to 21.0.1145.0 makes it compile with gcc-4.7 and fixes (I > haven't experienced any segfaults so far) the segfaults. These patches also work for me. (compiles and no segfaults) Created attachment 314359 [details, diff]
Patch from upstream
This applies cleanly to chromium-21.0.1163.0.
Upstream commit: http://src.chromium.org/viewvc/chrome?view=rev&revision=140470 @floppym: thanks, patch works They broke it again in 21.0.1171.0: ---- chrome/browser/memory_details_linux.cc:191:74: error: 'getpid' was not declared in this scope make: *** [out/Release/obj.target/browser/chrome/browser/memory_details_linux.o] Error 1 ---- And the above patch does not apply with that version. Created attachment 315639 [details, diff]
chromium-gcc-4.7-r1.patch
Right, but that's the only incompatibility in fact.
The patch I used to fix it is attached.
I'm getting the exact error message from the description with www-client/chromium-20.0.1132.43 and sys-devel/gcc-4.7.1. None of the patches mentioned here seem to apply to this version. (In reply to comment #19) I doubt we are going to fix chromium-20. Mike, due to this bug i'm stuck in 19.xx with security issues. while waiting for upstream I would propose you to adapt the patch for a 20xx release, and, even if chromium team is going to release new versions, have at least one gcc 4.7 compatibile version. is that feasable for you? (In reply to comment #21) > Mike, > due to this bug i'm stuck in 19.xx with security issues. > > while waiting for upstream I would propose you to adapt the patch for a 20xx > release, and, even if chromium team is going to release new versions, have > at least one gcc 4.7 compatibile version. > > is that feasable for you? If you are unmasking gcc, why don't you also go for chromium-21*? Works fine here. you're right but gcc 4.7.1 is considered stable upstream, chromium 21 not. anyway ill go for that solution. Release of Chrome 21 to the Stable Channel. 21.0.1180.57 for Mac and Linux. I hope it helps the stabilization process of GCC. This is fixed in the latest chromium dev channel. http://src.chromium.org/viewvc/chrome?view=rev&revision=148519 Can somebody bump the dev channel ebuild to google's latest chromium dev channel release? I'm able to successfully build chromium-22.0.1221.1 with gcc-4.7.1. |