Thread: Detecting proper bison version before make

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I just installed Postgres on an older machine and was surprised
that configure did not throw an error about running an old version
of bison, but let me get a bit into the whole 'make' cycle before
a cryptic error was thrown. Can the configure script be made to check
for a proper version of bison?

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200306012154
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+2q7qvJuQZxSWSsgRAjmqAKDOWFXmckpYnvrIXSKVY7CQNWcn2gCbBb7b
il6Rrr+MmQ4fUrFNN4dRNyM=
=2Y3s
-----END PGP SIGNATURE-----

Greg Sabino Mullane writes:

> Can the configure script be made to check for a proper version of bison?

Normally the parser files are prebuild and bison is never invoked.  So it
seems wasteful to do a bunch of checking for this rare case.

--
Peter Eisentraut   peter_e@gmx.net

Peter Eisentraut wrote:
> Greg Sabino Mullane writes:
>
> > Can the configure script be made to check for a proper version of bison?
>
> Normally the parser files are prebuild and bison is never invoked.  So it
> seems wasteful to do a bunch of checking for this rare case.

Well, someone asked for it, and we already check for bison, so we might
as well check for a version that actually works.  Now, if you are
suggesting we remove both bison checks, I could understand that.  Are
you?

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073