From: Tom Lane <tgl@sss.pgh.pa.us>
To: jwieck@debis.com
Cc: hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
Date: Wed, 28 Oct 1998 12:30:50 -0500
Message-ID: <19356.909595850@sss.pgh.pa.us> (raw)
In-Reply-To: <m0zYZ3f-000EBPC@orion.SAPserv.Hamburg.dsh.de>
jwieck@debis.com (Jan Wieck) writes:
> I asked for it a while ago but forgot about it. Anyway - I
> think it is better to have precreated gram.c, y.tab.h and
> scan.c files in src/pl/plpgsql/src too. Otherwise ppl not
> having bison/flex might have a build problem.
There are quite a few places that need lex/yacc capability; plpgsql
is not creating any new build requirement that did not exist before.
(ecpg and bootparse are two examples I can think of offhand.)
We ship the main gram.c file not to avoid requiring lex/yacc, but
because it is too big for some older yaccs.
It might be nice to eliminate the need for lex/yacc capability,
but post-beta3 is NOT the time to be doing "might be nice" stuff.
Leave it be for now.
regards, tom lane
PS: BTW, I was able to build all the Postgres yacc files on a rather
ancient HPUX yacc, once I added enough -N switches. According to my
notes,
YACC:/usr/bin/yacc
YFLAGS:-d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
worked with a pretty recent fileset. So I'm not sure we even really
need to distribute the main parser's gram.c. We could have configure
plug in these switches if it fails to find bison...
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jwieck@debis.com, hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
In-Reply-To: <19356.909595850@sss.pgh.pa.us>
* 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