From: Philip Yarra <philip@utiba.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ECPG CVS version problems
Date: Mon, 16 Jun 2003 15:58:13 +1000
Message-ID: <200306161558.13871.philip@utiba.com> (raw)
In-Reply-To: <26338.1055738104@sss.pgh.pa.us>
References: <200303280200.h2S20N218363@candle.pha.pa.us>
<200306161404.55749.philip@utiba.com>
<26338.1055738104@sss.pgh.pa.us>
On Mon, 16 Jun 2003 02:35 pm, Tom Lane wrote:
> Philip Yarra <philip@utiba.com> writes:
> > I just did a test build on a machine with bison 1.35, and there were no
> > complaints regarding its version
>
> You sure? I see [it] in configure's output
Oh, yes, well so it is. Sorry about that.
> (The reason it's not
> a hard error is that you don't actually need bison unless you don't have
> up-to-date copies of the derived files made by bison. This should not
> be the case when using a snapshot, only when building from a CVS pull.)
Provided preproc.y has changed... `make clean` does not remove the output of
bison, I found. When I copied the CVS source from my workstation to the
machine with older bison I didn't realise that, hence the confusion.
> > I assume that a way was found to make
> > older versions of bison work
>
> You assume wrong.
Yep. Part of the learning-curve, I suppose. I'll get there.
Regards, Philip.
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: philip@utiba.com, tgl@sss.pgh.pa.us, meskes@postgresql.org
Subject: Re: ECPG CVS version problems
In-Reply-To: <200306161558.13871.philip@utiba.com>
* 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