Bug 126883 - [GTK] Error building webkitgtk 2.3.4
Summary: [GTK] Error building webkitgtk 2.3.4
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-13 05:17 PST by Alberto Garcia
Modified: 2014-02-03 01:12 PST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Garcia 2014-01-13 05:17:35 PST 
Here's the output:

DerivedSources/WebCore/MathMLNames.cpp:641:66: error: 'Steral' has not been declared
     StringImpl::StaticASCIILiteral::s_initialFlags | (8634190 << Steral::s_hashShift)
                                                                  ^
DerivedSources/WebCore/MathMLNames.cpp:643:39: error: redefinition of 'WTF::StringImpl::StaticASCIILiteral WebCore::MathMLNames::mathbackgroundData'
 static StringImpl::StaticASCIILiteral mathbackgroundData = {
                                       ^
DerivedSources/WebCore/MathMLNames.cpp:216:39: error: 'WTF::StringImpl::StaticASCIILiteral WebCore::MathMLNames::mathbackgroundData' previously defined here
 static StringImpl::StaticASCIILiteral mathbackgroundData = {
                                       ^
DerivedSources/WebCore/MathMLNames.cpp: In function 'void WebCore::MathMLNames::init()':
DerivedSources/WebCore/MathMLNames.cpp:932:58: error: 'miData' was not declared in this scope
         { (void*)&miTag, *reinterpret_cast<StringImpl*>(&miData) },
                                                          ^
make[2]: *** [DerivedSources/WebCore/libWebCore_la-MathMLNames.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
Comment 1 Alberto Garcia 2014-01-13 08:28:30 PST 
Hmm... I regenerated MathMLNames.cpp and now it builds fine, I wonder what happened here. Two generator scripts running in parallel maybe?
Comment 2 Alberto Garcia 2014-02-03 01:12:04 PST 
I haven't seen this problem again and I've been able to build this release in several machines with different architectures, so I assume there was something wrong in my environment.