Re: cvs build failure

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Markus Bertheau <twanger(at)bluetwanger(dot)de>, Larry Rosenman <ler(at)lerctr(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: cvs build failure
Date: 2003-07-02 00:37:30
Message-ID: 200307020037.h620bU828245@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I can see making a new bison required only when the version is *devel.
> > That way, folks testing CVS and even the *devel snapshots would need a
> > new bison, but our normal users wouldn't.
>
> Even then, if they're using a snapshot they shouldn't need it.
>
> Perhaps a combination of your idea and Alvaro's: set things up so that
> we fail only when bison is actually invoked by the makefiles, plus
> provide a way to override the version check if it's wrong.

I don't see a reason to have a flag to turn it off --- has anyone
reported that the version check failed?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-07-02 01:40:01 Re: Urgent : Regarding Submission of Code
Previous Message Andrew Dunstan 2003-07-02 00:09:23 Re: cvs build failure