| 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: | Jonathan Scott <jwscott(at)vanten(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: simple make check failures |
| Date: | 2004-03-02 20:08:22 |
| Message-ID: | 200403022008.i22K8MB00891@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Jonathan Scott <jwscott(at)vanten(dot)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 that configuration 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(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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2004-03-02 20:44:38 | Re: IN and ANY |
| Previous Message | Bruce Momjian | 2004-03-02 18:45:21 | Re: [GENERAL] select statement against pg_stats returns |