Summary: | [Chromium] Build failure with clang | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Cosmin Truta <ctruta> | ||||||
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED DUPLICATE | ||||||||
Severity: | Normal | CC: | dglazkov, sgjesse, thakis | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Attachments: |
|
Description
Cosmin Truta
2010-11-02 10:55:37 PDT
Created attachment 72708 [details]
Fix
Here is the fix.
Since gcc doesn't issue this warning by default, would it not be worth adding -Wtype-limits (and possibly others) to all CFLAGS, to ensure a smoother gcc <-> clang transition in the future?
Comment on attachment 72708 [details]
Fix
ok.
Created attachment 72723 [details]
Fix (fixed)
Oops, I accidentally made changes in the wrong git branch, and my previous patch turned out backwards.
Here is the correct fix.
Comment on attachment 72723 [details]
Fix (fixed)
ok.
Isn't this what is already fixed by https://bugs.webkit.org/show_bug.cgi?id=48414? (In reply to comment #5) > Isn't this what is already fixed by https://bugs.webkit.org/show_bug.cgi?id=48414? Oh, yeah, it is... I had a 1-day-old copy of WebKit that I should have refreshed... Comment on attachment 72723 [details] Fix (fixed) Setting cq-. This was already fixed yesterday in bug 48414, and I haven't noticed. |