Problem solved. It turns out that the QtWebKit that my system had in /usr, was being used instead of my build. I had to 'cp' the QtWebKit manually, as I didn't find a script (like build-webkit) to install the newly built webkit? The Gtk port has 'make install', but how about the Qt port? Also, I am sure that there is a way to use a QtWebKit without installing it system-wide, could you please explain me how? Even after I had removed my system QtWebKit and rebuild WebKit from scratch, it was still not looking at QtWebKit in the build directory.
Benoit 2009/12/16 Benoit Jacob <[email protected]>: > Hi, > > Could you please help me with this error. I have just built webkit (qt > port on linux x86-64) in Release mode, and am trying to run the tests. > When I do: > > $ run-webkit-tests > > the result is that all tests report "crashed". To figure out what was > happening, I tried running the executable myself. AFAIU, the > executable is DumpRenderTree. After exporting the WEBKIT_TESTFONTS > environment variable, I was able to run it but got a symbol lookup > error: > > command: > > $ WebKitBuild/Release/bin/DumpRenderTree > LayoutTests/animations/animation-controller-drt-api.html > > result: > > WebKitBuild/Release/bin/DumpRenderTree: symbol lookup error: > WebKitBuild/Release/bin/DumpRenderTree: undefined symbol: > _Z33qt_drt_overwritePluginDirectoriesv > > If one demangles this name, this is just a function > qt_drt_overwritePluginDirectories(void). > > Any idea why it's missing? > Benoit > _______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
