Xref: utzoo comp.unix.questions:25263 comp.unix.internals:81 comp.unix.misc:13 comp.unix.sysv386:120 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!snorkelwacker!bloom-beacon!eru!hagbard!sunic!nuug!ifi!tore From: tore@ifi.uio.no (Tore Solvar Karlsen) Newsgroups: comp.unix.questions,comp.unix.internals,comp.unix.misc,comp.unix.sysv386 Subject: Re: yacc Problem on 386 based System V Keywords: System V 3.2.2 386 yacc Errors Message-ID: <1990Sep6.075450.2949@ifi.uio.no> Date: 6 Sep 90 07:54:50 GMT References: <2253@moscom.UUCP> Sender: tore@ifi.uio.no (Tore Solvar Karlsen) Reply-To: tore@ifi.uio.no (Tore Solvar Karlsen) Organization: Dept. of Informatics, University in Oslo, Norway Lines: 30 Nntp-Posting-Host: solvar.ifi.uio.no Originator: tore@solvar.ifi.uio.no In article , rob@dutncp8.tudelft.nl (Rob Kurver) writes: > > Some yacc's for 386s apear to be compiled with rather small tables (yes, > they appear to not allocate memory dynamically... heck, even the output > file name is fixed!). I had this same problem a few years back with my > Microport UNIX, at which time Microport was kind enough to offer a version > compiled with bigger tables. I now run Esix and have no problems with the > table sizes anymore. > > My guess is that this is your 'out of space' problem: one of the internal > tables is full. Perhaps you can talk your UNIX vendor into giving you a > yacc binary compiled with bigger tables. Yesteday, I ran into almost the same problem, trying to compile the last version of sc (scalc). The command "yacc -d foo.y " failed with an error message hinting about increasing some buffer space with a "-Sm#" option . Anyway, changing the command to "yacc -d -Sm10400 foo.y " made it, in this case... The "-S" option in yacc seems not to be documented in the manfile. OS: SCO unix 3.2 with development kit. Perhaps someone with more experience can give an explanation. -- Tore Solvar