Re: simple make check failures - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: simple make check failures
Date
Msg-id 200403022008.i22K8MB00891@candle.pha.pa.us
Whole thread Raw
In response to Re: simple make check failures  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: simple make check failures  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tom Lane wrote:
> Jonathan Scott <jwscott@vanten.com> writes:
> > I checked my system, and bison is reporting itself as 1.875. I am using SuSE 9.0, and I did have to upgrade to get
thatconfiguration message to go away, AND to make it compile. 
 
> 
> > Could you recommend a way I could get bison to reproduce that message?
> 
> If you did just upgrade bison, I'd suggest "make maintainer-clean" and
> then rebuild.  I do not think the Postgres makefiles are able to detect
> that you installed a new bison, so they won't automatically re-run bison
> to build new output files.  We normally ship the bison output files as
> part of distribution tarballs, which is why "make clean" or even "make
> distclean" doesn't flush 'em.

I have updated the text warning about too-old bison to be clearer when
it is a problem:

! *** If you are going to modify the lexer files or build from CVS, the installed
! *** version of Bison is too old.  Bison version 1.875 or later is required.])

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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] select statement against pg_stats returns
Next
From: Dennis Bjorklund
Date:
Subject: Re: IN and ANY