Re: [HACKERS] DEC OSF1 Compilation problems - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] DEC OSF1 Compilation problems
Date
Msg-id 36BA6466.CCDAEF7F@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] DEC OSF1 Compilation problems  ("Pedro J. Lobo" <pjlobo@euitt.upm.es>)
Responses Re: [HACKERS] DEC OSF1 Compilation problems
Re: [HACKERS] DEC OSF1 Compilation problems
List pgsql-hackers
> >2. gram.y did not compile by yacc (on FreeBSD too)
> ># woland(dms)~/postgresql-6.4.2/src/backend/parser>yacc -d gram.y
> ># yacc: f - maximum table size exceeded
> >fixed by using bison
> I had always used bison. I will add this to the DU FAQ.

This should not be required in principle, but it is easy with cvs to
accidentally get the time tags on gram.y and gram.c out of sync, so that
a "cvs checkout" causes Make to think gram.c needs to be rebuilt. I
think that v6.4.2 ended up with the times out of sync, as have other
releases in the past.

The other large parser, for ecpg, should probably ship both .y and .c
files, but does not yet, so perhaps bison needs to be used anyway. We
should fix this in an upcoming release.

To fix the cvs checkout problem, we might consider having a canned
routine which updates these time tags after a cvs checkout and before
the tar file is constructed...
                - Tom


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Backend problem with large objects
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] DEC OSF1 Compilation problems