Re: cvs build failure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: cvs build failure
Date
Msg-id 22415.1057097551@sss.pgh.pa.us
Whole thread Raw
In response to Re: cvs build failure  (Markus Bertheau <twanger@bluetwanger.de>)
Responses Re: cvs build failure  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Re: cvs build failure  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Markus Bertheau <twanger@bluetwanger.de> writes:
>> what version of bison are you using?  I believe we require 1.875 these days.

> 1.35. I'll upgrade. Thanks.

I believe 'configure' will bleat about a too-old bison, but it won't
refuse to proceed --- and the warning is easy to miss in the pages of
output that configure produces.

I was against having configure error out if bison is too old, since
you might not need it at all (if building from a tarball).  But it
seems like we still have the problem.

Maybe make configure act as though bison is missing?  Not sure.  It
seems like that could create unnecessary problems in other cases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: make check fails: user "postgres" doesn't exist
Next
From: Tom Lane
Date:
Subject: Re: Index expressions: how to recreate