I'm having trouble compiling the current cvs version on windows xp (msvc 2005 
express). Compile errors below.

I have bison 1.875 (I can't find 2.2+ for windows) and flex 2.5.4. These tools 
seem to generate correct outputs.

It looks like it might be including parse.h from include/parser/parse.h instead 
of src/backend/parser/parse.h. Are these two files supposed to be identical? 
NULLS_P, etc is defined in the latter, but not the former. If I manually copy 
the file over, compilation succeeds (still struggling with linking).

Here are the compile errors:
        
        Build started: Project: postgres, Configuration: Release|Win32
        Running bison on src\backend\parser\gram.y
                1 file(s) copied.
        Running flex on src\backend\parser\scan.l
        Compiling...
        parser.c
        .\src\backend\parser\parser.c(100): error C2065: 'NULLS_P' : undeclared 
identifier
        .\src\backend\parser\parser.c(100): error C2051: case expression not 
constant
        .\src\backend\parser\parser.c(111): error C2065: 'NULLS_FIRST' : 
undeclared identifier
        .\src\backend\parser\parser.c(114): error C2065: 'NULLS_LAST' : 
undeclared identifier
        keywords.c
        .\src\backend\parser\keywords.c(45): error C2065: 'ALWAYS' : undeclared 
identifier
        .\src\backend\parser\keywords.c(45): error C2099: initializer is not a 
constant
        .\src\backend\parser\keywords.c(90): error C2065: 'CONFIGURATION' : 
undeclared identifier
        .\src\backend\parser\keywords.c(90): error C2099: initializer is not a 
constant
        .\src\backend\parser\keywords.c(94): error C2065: 'CONTENT_P' : 
undeclared identifier
        .\src\backend\parser\keywords.c(94): error C2099: initializer is not a 
constant

thanks!
--craig





      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to