| Summary: | webkit gtk 2.2.3 stable tarball compilation error | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | aditya <aditya.l> | ||||||
| Component: | WebKitGTK | Assignee: | Zan Dobersek <zan> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | mrobinson, zan | ||||||
| Priority: | P2 | ||||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Other | ||||||||
| OS: | Linux | ||||||||
| Attachments: |
|
||||||||
Ugh, this is due to a shortcoming in the code. A speculative build fix coming shortly -- you can try it out for yourself, though I won't be able to try it out for myself until later today. Created attachment 219633 [details]
Patch
The patch is working fine. The error is resolved. Thanks. OK, cool. I'll get this reviewed, landed and merged into the 2.2 branch. Comment on attachment 219633 [details] Patch Clearing flags on attachment: 219633 Committed r160997: <http://trac.webkit.org/changeset/160997> All reviewed patches have been landed. Closing bug. |
Created attachment 219632 [details] configuration log file I am trying to install webkit gtk 2.2.3 stable tarball on kubuntu 13.04 64-bit machine. I tried running ./configure as, 1) ./configure 2) ./configure --enable-accelerated-compositing=no After completing configuration without any error (for both the ./configure commands), I tried ./make, for which I got following error message. Source/WebCore/platform/graphics/GLContext.cpp: In static member function 'static WTF::PassOwnPtr<WebCore::GLContext> WebCore::GLContext::createContextForWindow(GLNativeWindowType, WebCore::GLContext*)': Source/WebCore/platform/graphics/GLContext.cpp:155:39: error: 'GDK_IS_WAYLAND_DISPLAY' was not declared in this scope make[1]: *** [Source/WebCore/platform/graphics/libPlatformGtk_la-GLContext.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/home/hbbtv/Downloads/webkitgtk-2.2.3' make: *** [all] Error 2 I am attaching config.log file with this request. Please inform if any there is any solution / patch available for this error. Regards.