Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.1/8.9.1) with ESMTP id MAA11783 for ; Wed, 28 Oct 1998 12:31:28 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA19358; Wed, 28 Oct 1998 12:30:50 -0500 (EST) To: jwieck@debis.com (Jan Wieck) cc: hackers@postgreSQL.org Subject: Re: [HACKERS] Open 6.4 items In-reply-to: Your message of Wed, 28 Oct 1998 18:06:55 +0100 (MET) Date: Wed, 28 Oct 1998 12:30:50 -0500 Message-ID: <19356.909595850@sss.pgh.pa.us> From: Tom Lane 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...