Summary: | [Qt] Build error in module WebKit/qt/tests/qwebelement/tst_qwebelement.cpp | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Clemmitt Sigler <cmsigler> | ||||
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | ||||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
Clemmitt Sigler
2009-04-11 13:31:32 PDT
(In reply to comment #0) Hi again, Bad form to reply to oneself and all, but anyway. I see that as of a few weeks ago the Buildbot setup at build.webkit.org changed. Now only OS X and Windows builds are running there. Are there any plans to add back build slaves for the Linux GTK+ and Linux Qt builds (and perhaps even the Linux wxWindows build, if that's appropriate)? Or maybe these build slaves have moved to another buildbot hosted elsewhere? Heaven knows I searched for another one via Google without success. This seems an appropriate place to ask, since build errors like this one aren't caught if no buildbot is running for this platform, eh? Thanks again very much :^) Clemmitt (In reply to comment #0) > As of r42423, the Qt Linux build fails with a compile error: Well, since my own Qt Linux build at r42550 was still failing in tst_qwebelement.cpp, I took a stab in the dark that the developer meant to use the method "size" for class QList instead of "length" which is undefined. This, at least, got my build to complete without failing on an error. A patch is attached next. (There may be another bug, this time in the Acid3 test. If so, I'll file a separate bug report on it. For now, my Qt Linux build crashes reliably near the end of running Acid3. I'll wait a few days to see if things settle down and this problem goes away.) HTH. Clemmitt Created attachment 29515 [details]
Patch to fix Qt Linux build error in module tst_qwebelement.cpp
This patch fixes a build error under Qt Linux in module tst_qwebelement.cpp. I think this is what the developer who wrote this module was aiming for....
Similar fix has been independently landed in http://trac.webkit.org/changeset/42608 *** This bug has been marked as a duplicate of 25242 *** |