From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Philip Yarra <philip@utiba.com>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ECPG CVS version problems
Date: Mon, 16 Jun 2003 01:18:24 -0400
Message-ID: <26607.1055740704@sss.pgh.pa.us> (raw)
In-Reply-To: <200306160507.h5G57xu20800@candle.pha.pa.us>
References: <200306160507.h5G57xu20800@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I wonder is we should check for *dev on the version string and make
> missing bison version a hard error in these cases.
No, because that breaks snapshot tarballs.
You could possibly make some argument for going out and actually
checking the existence and timestamp of each bison-derived file that
should be there, and erroring out only if it looks like bison is really
gonna get invoked during the build. But that seems like an
unmaintainable kluge to me.
It's not like the bison-related build failures aren't pretty obvious.
I think the configure-time test is doing its job by producing a
warning. If people don't notice it, well, they'll find out later.
We do assume some level of technical competence for those who build
from CVS pulls ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, philip@utiba.com, meskes@postgresql.org
Subject: Re: ECPG CVS version problems
In-Reply-To: <26607.1055740704@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox