Bug 116705 - [GTK] Unable to build webkit 2.0.2 libWebExtensionTest.la
Summary: [GTK] Unable to build webkit 2.0.2 libWebExtensionTest.la
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-24 00:09 PDT by Funda Wang
Modified: 2014-09-19 09:45 PDT (History)
2 users (show)

See Also:


Attachments
config.log (96.70 KB, text/plain)
2013-05-24 02:57 PDT, Funda Wang
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Funda Wang 2013-05-24 00:09:17 PDT
I'm currently building webkit 2.0.2 (webkit2) under mageia cauldron, but failed with following errors:

Libraries/.libs/../../Source/WebKit2/UIProcess/API/gtk/tests/.libs/Libraries_libWebKit2APITestCore_la-TestMain.o: In function `main':
TestMain.cpp:(.text.startup+0x129): undefined reference to `beforeAll()'
TestMain.cpp:(.text.startup+0x137): undefined reference to `afterAll()'
collect2: error: ld returned 1 exit status
make[1]: *** [Libraries/WebExtensions/libWebExtensionTest.la] Error 1

How to make it build?
Comment 1 Zan Dobersek 2013-05-24 00:24:01 PDT
Can you please attach the config.log file?
Comment 2 Funda Wang 2013-05-24 01:02:29 PDT
And, then, there are another failure:

./.libs/../Source/WebCore/platform/.libs/libWebCorePlatform_la-ThreadGlobalData.o: In function `WebCore::ThreadGlobalData::ThreadGlobalData()':
ThreadGlobalData.cpp:(.text+0x24a): undefined reference to `WebCore::CachedResourceRequestInitiators::CachedResourceRequestInitiators()'
ThreadGlobalData.cpp:(.text+0x262): undefined reference to `WebCore::EventNames::EventNames()'
./.libs/../Source/WebCore/platform/graphics/freetype/.libs/libWebCoreGtk2_la-FontPlatformDataFreeType.o: In function `WebCore::FontPlatformData::operator=(WebCore::FontPlatformData const&)':
FontPlatformDataFreeType.cpp:(.text+0x244): undefined reference to `WebCore::HarfBuzzFace::~HarfBuzzFace()'
./.libs/../Source/WebCore/platform/graphics/freetype/.libs/libWebCoreGtk2_la-FontPlatformDataFreeType.o: In function `WebCore::FontPlatformData::~FontPlatformData()':
FontPlatformDataFreeType.cpp:(.text+0x2f4): undefined reference to `WebCore::HarfBuzzFace::~HarfBuzzFace()'
./.libs/../Source/WebCore/platform/graphics/freetype/.libs/libWebCoreGtk2_la-FontPlatformDataFreeType.o: In function `WebCore::FontPlatformData::harfBuzzFace() const':
FontPlatformDataFreeType.cpp:(.text+0x3be): undefined reference to `WebCore::HarfBuzzFace::HarfBuzzFace(WebCore::FontPlatformData*, unsigned long)'
FontPlatformDataFreeType.cpp:(.text+0x3f4): undefined reference to `WebCore::HarfBuzzFace::~HarfBuzzFace()'
./.libs/../Source/WebCore/platform/graphics/gstreamer/.libs/libWebCoreGtk2_la-MediaPlayerPrivateGStreamer.o: In function `WebCore::initializeGStreamerAndRegisterWebKitElements()':
MediaPlayerPrivateGStreamer.cpp:(.text+0x98b): undefined reference to `webkit_web_src_get_type'
./.libs/../Source/WebCore/platform/graphics/gstreamer/.libs/libWebCoreGtk2_la-MediaPlayerPrivateGStreamer.o: In function `WebCore::MediaPlayerPrivateGStreamer::sourceChanged()':
MediaPlayerPrivateGStreamer.cpp:(.text+0x16ca): undefined reference to `webkit_web_src_get_type'
MediaPlayerPrivateGStreamer.cpp:(.text+0x1705): undefined reference to `webkit_web_src_get_type'
MediaPlayerPrivateGStreamer.cpp:(.text+0x171f): undefined reference to `webKitWebSrcSetMediaPlayer'
collect2: error: ld returned 1 exit status
make[1]: *** [Programs/WebKitPluginProcess] Error 1
Comment 3 Funda Wang 2013-05-24 02:57:40 PDT
Created attachment 202796 [details]
config.log
Comment 4 Zan Dobersek 2013-06-17 13:16:25 PDT
I see in config.log that there are additional patches being applied. Are they necessary? Can you share them?

As far as I can see, apart from the patches, config.log doesn't provide anything suspicious.
Comment 5 Philippe Normand 2014-09-19 09:45:01 PDT
The autotools build system was replaced by CMake, can you please try again and reopen the bug if the issue still exists for you?