Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA68614;
	Tue, 12 Oct 1999 10:37:52 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA16415;
	Tue, 12 Oct 1999 10:36:39 -0400 (EDT)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org,
	pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] bison 
In-reply-to: Your message of Tue, 12 Oct 1999 05:43:02 +0000
	<3802CA66.C08B5B05@alumni.caltech.edu>
Date: Tue, 12 Oct 1999 10:36:39 -0400
Message-ID: <16413.939738999@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> You might want to include into the installation instructions (or whereever
>> it will end up) that GNU bison 1.25 is required. (right after the flex
>> stuff)

> We haven't been careful about building and shipping the bison output
> in the tarball distribution, as we have for the main parser.

Huh?  src/tools/release_prep automatically builds both the main parser
and ecpg bison output files.  Is there other stuff it should be
handling too?

			regards, tom lane