Error-out on compiling current CVS: preproc
Folks,
Got the following bomb trying to build from current CVS (August 8th):
make[4]: Leaving directory `/usr/src/postgresql-8.0b/src/interfaces/ecpg/
compatlib'
make -C preproc all
make[4]: Entering directory `/usr/src/postgresql-8.0b/src/interfaces/ecpg/
preproc'
make -C ../../../../src/port all
make[5]: Entering directory `/usr/src/postgresql-8.0b/src/port'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/usr/src/postgresql-8.0b/src/port'
bison -y -d preproc.y
preproc.y:4850.24-4853.22: type clash (`str' `keyword') on default action
preproc.y:4853.23: parse error, unexpected ":", expecting ";" or "|"
make[4]: *** [preproc.h] Error 1
make[4]: Leaving directory `/usr/src/postgresql-8.0b/src/interfaces/ecpg/
preproc'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/postgresql-8.0b/src/interfaces/ecpg'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/postgresql-8.0b/src/interfaces'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/postgresql-8.0b/src'
make: *** [all] Error 2
Setup:
SuSE 9.0, GCC 3.3.1, Bison 1.75 on Celeron Thinkpad
Basic configure and make, no options except --prefix=/usr/local/pg80b
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Folks,
Update on this: Just tried it with:
SuSE 9.1, GCC 3.3.3, Bison 1.875
and don't get the error.
So it looks like the requirement for Bison 1.85+ is now a "hard" requirement?
We'll need to document this, since SuSE 9.0 is less than a year old, and I'm
sure some other distros are still using 1.75.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Josh Berkus wrote:
Folks,
Update on this: Just tried it with:
SuSE 9.1, GCC 3.3.3, Bison 1.875
and don't get the error.So it looks like the requirement for Bison 1.85+ is now a "hard" requirement?
We'll need to document this, since SuSE 9.0 is less than a year old, and I'm
sure some other distros are still using 1.75.
I see in configure.in:
AC_CHECK_PROGS(YACC, ['bison -y'])
if test "$YACC"; then
if $YACC --version | sed q | $AWK '{ if ($4 < 1.875) exit 0; else exit 1;}'; then
AC_MSG_WARN([
*** If you are going to modify the grammar files or build from CVS, the installed
*** version of Bison is too old. Bison version 1.875 or later is required.])
fi
fi
Looks documented to me.
--
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 19073Bruce,
*** If you are going to modify the grammar files or build from CVS, the
installed *** version of Bison is too old. Bison version 1.875 or later is
required.]) fi
fi
Aha. Yeah, blew past me too fast to read. Hmmm ... does that mean that this
error won't happen in the release version?
--
Josh Berkus
Aglio Database Solutions
San Francisco
Josh Berkus wrote:
Bruce,
*** If you are going to modify the grammar files or build from CVS, the
installed *** version of Bison is too old. Bison version 1.875 or later is
required.]) fi
fiAha. Yeah, blew past me too fast to read. Hmmm ... does that mean that this
error won't happen in the release version?
I think so. The only reason you need bison in the release version is if
you modify the grammar files.
--
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
Josh Berkus wrote:
Aha. Yeah, blew past me too fast to read. Hmmm ... does that mean that this
error won't happen in the release version?
You shoouldn't need bison at all with a release tarball -- the
preprocessed grammar file is distributed with it.
Joe
Bruce Momjian <pgman@candle.pha.pa.us> writes:
I see in configure.in:
*** If you are going to modify the grammar files or build from CVS, the installed
*** version of Bison is too old. Bison version 1.875 or later is required.])
Looks documented to me.
Also, installation.sgml specifically says 1.875 or newer, and the 7.4
release notes already said 1.85 is required. I don't know where else
we would document it?
regards, tom lane