[HACKERS] Bison Version
What version of Bison is currently required to compile HEAD? 1.75 doesn't seem to work... ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Bison Version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What version of Bison is currently required to compile HEAD? 1.75 doesn't seem to work... 1.875 Search for Bison here: http://projects.commandprompt.com/public/pgsql/browser/trunk/pgsql/doc/src/sgml/installation.sgml - -- Greg Sabino Mullane [EMAIL PROTECTED] End Point Corporation PGP Key: 0x14964AC8 200608110905 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -BEGIN PGP SIGNATURE- iD8DBQFE3IEivJuQZxSWSsgRAlflAJ9ZqKPKyrav/Ln7vjSgFzBEyorfgACgw0vJ OMR3lJzf5MP1mhzVdlVDZG4= =Oz63 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Bison Version
Christopher Kings-Lynne wrote: What version of Bison is currently required to compile HEAD? 1.75 doesn't seem to work... Bison = 1.875 has been required for years. That hasn't changed. cheers andrew ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Bison Version
Due to the bug in bison 2.1, I always use version 1.875: http://www.mail-archive.com/bug-bison@gnu.org/msg00718.html Christopher Kings-Lynne [EMAIL PROTECTED] What version of Bison is currently required to compile HEAD? 1.75 doesn't seem to work... ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] bison version
Hi Stefan, Here's my make.log FWIW... TIA On Sat, 10 Jun 2006, Stefan Kaltenbrunner wrote: Date: Sat, 10 Jun 2006 21:10:09 +0200 From: Stefan Kaltenbrunner [EMAIL PROTECTED] To: ohp@pyrenet.fr Cc: PostgreSQL-development pgsql-hackers@postgresql.org Subject: Re: [HACKERS] bison version ohp@pyrenet.fr wrote: Hi, I'd like to check 2 things: What's the bison version required to compile gram.y ? Trying to set up a build farm machine, it seems I can't compile with bison 2.1 ... 2.1 should work fine - there are a number of boxes on the buildfarm running with that version (like sponge the FC5/ppc I own). What exact problem do you see on your platform ? Also where is the documentation page that gives postgresql limits (number of column/table max size of col) http://www.postgresql.org/docs/faqs.FAQ.html#item4.4 Stefan -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges+33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp@pyrenet.fr -- Make your life a dream, make your dream a reality. (St Exupery)gmake -C doc all gmake[1]: Entering directory `/home4/ohp/pgfarmbuild/HEAD/pgsql.4903/doc' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home4/ohp/pgfarmbuild/HEAD/pgsql.4903/doc' gmake -C src all gmake[1]: Entering directory `/home4/ohp/pgfarmbuild/HEAD/pgsql.4903/src' gmake -C port all gmake[2]: Entering directory `/home4/ohp/pgfarmbuild/HEAD/pgsql.4903/src/port' ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o getopt_long.o getopt_long.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o copydir.o copydir.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o dirmod.o dirmod.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o exec.o exec.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o noblock.o noblock.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled echo #define PGBINDIR \/home4/ohp/pgfarmbuild/HEAD/inst/bin\ pg_config_paths.h echo #define PGSHAREDIR \/home4/ohp/pgfarmbuild/HEAD/inst/share/postgresql\ pg_config_paths.h echo #define SYSCONFDIR \/home4/ohp/pgfarmbuild/HEAD/inst/etc/postgresql\ pg_config_paths.h echo #define INCLUDEDIR \/home4/ohp/pgfarmbuild/HEAD/inst/include\ pg_config_paths.h echo #define PKGINCLUDEDIR \/home4/ohp/pgfarmbuild/HEAD/inst/include/postgresql\ pg_config_paths.h echo #define INCLUDEDIRSERVER \/home4/ohp/pgfarmbuild/HEAD/inst/include/postgresql/server\ pg_config_paths.h echo #define LIBDIR \/home4/ohp/pgfarmbuild/HEAD/inst/lib\ pg_config_paths.h echo #define PKGLIBDIR \/home4/ohp/pgfarmbuild/HEAD/inst/lib/postgresql\ pg_config_paths.h echo #define LOCALEDIR \\ pg_config_paths.h echo #define DOCDIR \/home4/ohp/pgfarmbuild/HEAD/inst/doc/postgresql\ pg_config_paths.h echo #define MANDIR \/home4/ohp/pgfarmbuild/HEAD/inst/man\ pg_config_paths.h ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o path.o path.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o pipe.o pipe.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o pgsleep.o pgsleep.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled ccache cc -O -Kinline -g -I../../src/port -DFRONTEND -I../../src/include -I/usr/local/include -c -o pgstrcasecmp.o pgstrcasecmp.c UX:cc: WARNING: debugging and optimization mutually exclusive; -O disabled UX:cc: WARNING: debugging
Re: [HACKERS] bison version
ohp@pyrenet.fr writes:
Here's my make.log FWIW...
...
gram.y:7074.27-7077.33: warning: useless rule: b_expr: b_expr IS OF '('
type_list ')'
gram.y:7078.27-7081.33: warning: useless rule: b_expr: b_expr IS NOT OF '('
type_list ')'
gmake[3]: *** [parse.h] Segmentation Fault (core dumped)
The fact that bison dumps core after emitting all those bogus
messages suggests to me that you've got a broken copy of bison.
regards, tom lane
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [HACKERS] bison version
Yep!
I reverted to 1.875 and it works, I'll be a member of build farm soon for
UnixWare.
On Sun, 11 Jun 2006, Tom Lane wrote:
Date: Sun, 11 Jun 2006 11:21:20 -0400
From: Tom Lane [EMAIL PROTECTED]
To: ohp@pyrenet.fr
Cc: Stefan Kaltenbrunner [EMAIL PROTECTED],
PostgreSQL-development pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] bison version
ohp@pyrenet.fr writes:
Here's my make.log FWIW...
...
gram.y:7074.27-7077.33: warning: useless rule: b_expr: b_expr IS OF '('
type_list ')'
gram.y:7078.27-7081.33: warning: useless rule: b_expr: b_expr IS NOT OF '('
type_list ')'
gmake[3]: *** [parse.h] Segmentation Fault (core dumped)
The fact that bison dumps core after emitting all those bogus
messages suggests to me that you've got a broken copy of bison.
regards, tom lane
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges+33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp@pyrenet.fr
--
Make your life a dream, make your dream a reality. (St Exupery)
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
[HACKERS] bison version
Hi, I'd like to check 2 things: What's the bison version required to compile gram.y ? Trying to set up a build farm machine, it seems I can't compile with bison 2.1 ... Also where is the documentation page that gives postgresql limits (number of column/table max size of col) Many thanks -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges+33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp@pyrenet.fr -- Make your life a dream, make your dream a reality. (St Exupery) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] bison version
ohp@pyrenet.fr wrote: Hi, I'd like to check 2 things: What's the bison version required to compile gram.y ? Trying to set up a build farm machine, it seems I can't compile with bison 2.1 ... 2.1 should work fine - there are a number of boxes on the buildfarm running with that version (like sponge the FC5/ppc I own). What exact problem do you see on your platform ? Also where is the documentation page that gives postgresql limits (number of column/table max size of col) http://www.postgresql.org/docs/faqs.FAQ.html#item4.4 Stefan ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] bison version
ohp@pyrenet.fr wrote: Hi, I'd like to check 2 things: What's the bison version required to compile gram.y ? Trying to set up a build farm machine, it seems I can't compile with bison 2.1 ... 1.875 Also where is the documentation page that gives postgresql limits (number of column/table max size of col) FAQ. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
