Bug 9340 – WebCore build failure due to cssgrammary.y errors

• Status: RESOLVED
• Resolution: INVALID
• Component: CSS

[Egor Margineanu]

c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(86) : error C3861: 'findProp': identifier not found
c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(90) : error C2027: use of undefined type 'WebCore::getPropertyID::props'
        c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(86) : see declaration of 'WebCore::getPropertyID::props'
c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(90) : error C2227: left of '->id' must point to class/struct/union/generic type
c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(111) : error C3861: 'findValue': identifier not found
c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(115) : error C2027: use of undefined type 'getValueID::css_value'
        c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(111) : see declaration of 'getValueID::css_value'
c:\cygdrive\c\libs\svn-we~1\webcore\css\cssgrammar.y(115) : error C2227: left of '->id' must point to class/struct/union/generic type

[David Kilzer (:ddkilzer)]

The buildbot for Windows doesn't seem to be affected:  http://build.webkit.org/

What versions of flex and/or bison do you have installed in Cygwin?

[Egor Margineanu]

(In reply to comment #1)
> The buildbot for Windows doesn't seem to be affected:  http://build.webkit.org/
> 
> What versions of flex and/or bison do you have installed in Cygwin?
> 

I have installed:
Bison 2.1 and Flex 2.5.4

[Mark Rowe (bdash)]

Egor, are you still having this issue?  The Windows buildslave for WebKit does not fail with this error, and the Mac OS X and Linux builds also handle cssgrammar.y fine.

[Egor Margineanu]

(In reply to comment #3)
> Egor, are you still having this issue?  The Windows buildslave for WebKit does
> not fail with this error, and the Mac OS X and Linux builds also handle
> cssgrammar.y fine.
> 

no, now all is ok. I think it was my mistake in configuring build process.
Thanks for help.

[George Staikos]

*** Bug 14841 has been marked as a duplicate of this bug. ***