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

From Tom Lane
Subject Re: simple make check failures
Date
Msg-id 9536.1077776142@sss.pgh.pa.us
Whole thread Raw
In response to Re: simple make check failures  (Jonathan Scott <jwscott@vanten.com>)
Responses Re: simple make check failures
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jonathan Scott
Date:
Subject: Re: simple make check failures
Next
From: Michael Meskes
Date:
Subject: Re: CVS HEAD compile warning