Re: [HACKERS] backend/parser compile prob

2003-07-19 Thread itojun
>Answer is: a broken flex 2.5.4. There were some commits to NetBSD flex to >use bounded strings. Using 13th July flex source builds a happy PostgreSQL. >Now to track down which bit broke - anyway, not a PostgreSQL problem :-) could you try usr.bin/lex/initscan.c revision 1.16? itojun ---

Re: [HACKERS] backend/parser compile prob

2003-07-19 Thread itojun
>> could you try lex/scan.l 1.13 i just committed? >Yes, that fixed it! tnx for reporting! itojun ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] backend/parser compile prob

2003-07-16 Thread Patrick Welche
On Wed, Jul 16, 2003 at 11:58:01PM +0900, [EMAIL PROTECTED] wrote: > could you try lex/scan.l 1.13 i just committed? Yes, that fixed it! Cheers, Patrick ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] backend/parser compile prob

2003-07-16 Thread Patrick Welche
On Tue, Jul 15, 2003 at 12:42:45PM -0400, Tom Lane wrote: > Patrick Welche <[EMAIL PROTECTED]> writes: ... > > What string constant?! Will try again later... > > Which flex version are you using? You need 2.5.4 --- the most recent > versions have broken backwards compatibility :-(. I'm not sure

Re: [HACKERS] backend/parser compile prob

2003-07-15 Thread Tom Lane
Patrick Welche <[EMAIL PROTECTED]> writes: > /usr/bin/flex -CF -o'scan.c' scan.l > gcc -O2 -pipe -g -Wall -Wmissing-prototypes -Wmissing-declarations -I. > -I../../../src/include -c -o gram.o gram.c > In file included from gram.y:7990: > scan.c:121: parse error before string constant > scan.c:24

Re: [HACKERS] backend/parser compile prob

2003-07-15 Thread Patrick Welche
On Tue, Jul 15, 2003 at 11:21:51AM -0400, Tom Lane wrote: > Patrick Welche <[EMAIL PROTECTED]> writes: > > I'm getting far too many errors while trying to compile gram.c in the > > backend/parser, that I must be missing something. > > I think you need to force gram.c to be regenerated. Try removi

Re: [HACKERS] backend/parser compile prob

2003-07-15 Thread Tom Lane
Patrick Welche <[EMAIL PROTECTED]> writes: > I'm getting far too many errors while trying to compile gram.c in the > backend/parser, that I must be missing something. I think you need to force gram.c to be regenerated. Try removing it (and parse.h too) before building. > % cvs diff src/backend/p

[HACKERS] backend/parser compile prob

2003-07-15 Thread Patrick Welche
I'm getting far too many errors while trying to compile gram.c in the backend/parser, that I must be missing something.. Story so far gmake distclean cvs update configure --enable-debug --enable-cassert gmake gmake[3]: Entering directory `/usr/src/local/pgsql/src/backend/parser' gcc -O2 -pipe -g -