Summary: | www-client/chromium fails to build with GCC 4.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Bernard Cafarelli <voyageur> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bruno, phajdan.jr, truedfx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 296658 | ||
Attachments: |
Build log (compressed)
patch |
Description
Diego Elio Pettenò (RETIRED)
2010-04-25 19:05:24 UTC
Created attachment 229123 [details]
Build log (compressed)
Created attachment 229127 [details, diff]
patch
This is the patch I've been using, already reported upstream.
(In reply to comment #2) > Created an attachment (id=229127) [details] > patch > > This is the patch I've been using, already reported upstream. Thanks. Could you post the link somewhere here? Chromium upstream moves so fast that I hope we can just pick up the fix with the next version bump. Hey truedfx, long time no see :) In trunk at least it's fixed here: http://src.chromium.org/viewvc/chrome?view=rev&revision=40900 (and dev channel 5.0.375.9 has it) I've added the patch to 5.0.342.9 (beta channel) in the meantime (In reply to comment #3) > Thanks. Could you post the link somewhere here? Chromium upstream moves so fast > that I hope we can just pick up the fix with the next version bump. http://code.google.com/p/seccompsandbox/issues/detail?id=1 Reported back in December. (In reply to comment #4) > Hey truedfx, long time no see :) I'm still around, just not as active as I probably should be :) > In trunk at least it's fixed here: > http://src.chromium.org/viewvc/chrome?view=rev&revision=40900 > (and dev channel 5.0.375.9 has it) > > I've added the patch to 5.0.342.9 (beta channel) in the meantime Good that it's fixed already, but I guess that means it's of no use reporting bugs upstream. (In reply to comment #5) > Good that it's fixed already, but I guess that means it's of no use reporting > bugs upstream. Oh, did you know it's the only bug ever reported to the "seccompsandbox" project? To make sure your patch gets included upstream, make sure to use http://codereview.chromium.org/ and then pick some reviewers and send them review e-mail (Publish+Mail comments). In case no one responds, you can contact me (I'm also a committer upstream, in chromium). |