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: | Markus Bertheau <twanger(at)bluetwanger(dot)de>, Larry Rosenman <ler(at)lerctr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: cvs build failure |
Date: | 2003-07-02 04:56:05 |
Message-ID: | 200307020456.h624u5e20667@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > This would turn off the make failure when an old bison is called from
> > the makefile?
>
> Rephrase that as "this would give bison the right to fail of its own
> accord, rather than our prejudging its ability to cope."
>
> Given bison's on-again-off-again track record in recent releases,
> I don't think it's wise to wire in a non-overridable assumption
> that bison < X is broken and bison >= X is good. A hint that
> bison < X might be broken is fine --- but let's not pretend that
> configure is smarter than the user.
I just don't like to add bloat/document another configure option that
has a _very_ limited usefulness. Can we not document it and just print
it when we report the bison failure? Should we just allow an environment
variable to over-ride it?
--
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 | Craig Jensen | 2003-07-02 05:20:57 | help with rpm script |
Previous Message | Tom Lane | 2003-07-02 04:45:02 | Re: cvs build failure |