X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 7D67730D174 for ; Mon, 16 Jun 2003 05:18:39 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 30689-08 for ; Mon, 16 Jun 2003 02:18:29 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E647930EDBB for ; Mon, 16 Jun 2003 02:18:28 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h5G5IPU6026608; Mon, 16 Jun 2003 01:18:25 -0400 (EDT) To: Bruce Momjian Cc: Philip Yarra , Michael Meskes , pgsql-interfaces@postgresql.org Subject: Re: ECPG CVS version problems In-reply-to: <200306160507.h5G57xu20800@candle.pha.pa.us> References: <200306160507.h5G57xu20800@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 16 Jun 2003 01:07:59 -0400" Date: Mon, 16 Jun 2003 01:18:24 -0400 Message-ID: <26607.1055740704@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/39 X-Sequence-Number: 4250 Bruce Momjian 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