Re: cvs build failure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: cvs build failure
Date
Msg-id 22725.1057099355@sss.pgh.pa.us
Whole thread Raw
In response to Re: cvs build failure  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: cvs build failure  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: cvs build failure  (Markus Bertheau <twanger@bluetwanger.de>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> Maybe make configure act as though bison is missing?  Not sure.  It
>> seems like that could create unnecessary problems in other cases.

> One trick would be to set YACC to some special value like
> "bison.too.old" and test for that when YACC is actually called from the
> Makefile.

I kinda like Alvaro's suggestion of an --ignore-bison-version option
to configure to suppress checking the version, but otherwise error out
if we think bison is too old.

The advantage to that is that you could manually override the automatic
check if you had reason to know it was wrong (eg, you could see it'd
misparsed the bison version string, or something).  Also, it'd make
sense to include that option by default in RPM builds, where you'd know
you had up-to-date bison output files already included in the SRPM.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: cvs build failure
Next
From: Manuel Sugawara
Date:
Subject: Re: cvs build failure