Re: [HACKERS] DEC OSF1 Compilation problems

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: pjlobo(at)euitt(dot)upm(dot)es, scrappy(at)hub(dot)org, dms(at)wplus(dot)net, pgsql-hackers(at)hub(dot)org, Michael(dot)Meskes(at)usa(dot)net
Subject: Re: [HACKERS] DEC OSF1 Compilation problems
Date: 1999-02-05 03:38:06
Message-ID: 199902050338.WAA25631@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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...

Is there some way to do this fixup in the makefile?

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-02-05 04:11:45 Re: [HACKERS] Adding some const keywords to external interfaces
Previous Message Thomas G. Lockhart 1999-02-05 03:24:22 Re: [HACKERS] DEC OSF1 Compilation problems