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 61C4030ED26; Mon, 16 Jun 2003 02:49:45 +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 33442-04; Sun, 15 Jun 2003 23:49:35 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 85C0D30EBF3; Sun, 15 Jun 2003 23:49:34 -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 h5G2nYU6025660; Sun, 15 Jun 2003 22:49:34 -0400 (EDT) To: Philip Yarra Cc: Michael Meskes , pgsql-interfaces@postgresql.org Subject: Re: ECPG CVS version problems In-reply-to: <200306161110.58418.philip@utiba.com> References: <200303280200.h2S20N218363@candle.pha.pa.us> <200304221345.40455.philip@utiba.com> <20030615110648.GH8944@feivel.fam-meskes.de> <200306161110.58418.philip@utiba.com> Comments: In-reply-to Philip Yarra message dated "Mon, 16 Jun 2003 11:10:58 +1000" Date: Sun, 15 Jun 2003 22:49:34 -0400 Message-ID: <25659.1055731774@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/35 X-Sequence-Number: 4246 Philip Yarra writes: > Bison 1.35 and 1.50 both have bugs that prevent successful compilation, > so I moved to 1.85. This appears to work okay. Is there some way during > configure to check for broken bison versions and complain loudly? Uh, this is done as of a few days ago. Or is the check not working? regards, tom lane