From bug-octave-request at bevo dot che dot wisc dot edu Wed Nov 4 18:24:22 1998 Subject: Unidentified subject! From: "John W. Eaton" To: michel at cepremap dot cnrs dot fr (Michel Juillard) Cc: bug-octave at bevo dot che dot wisc dot edu Date: Wed, 4 Nov 1998 16:59:11 -0600 (CST) On 4-Nov-1998, Michel Juillard wrote: | To: bug-octave at bevo dot che dot wisc dot edu | Cc: michel | Subject: [50 character or so descriptive subject here (for reference)] | -------- | Bug report for Octave 2.1.9 configured for %CANONICAL_HOST_TYPE% | | Description: | ----------- | error in compiling parse.cc with egcs-1.1b (Linux on i686): | | c++ -c -I. -I../../octave-2.1.9/src -I.. -I../liboctave -I../src -I../libcruft/misc -I../../octave-2.1.9 -I../../octave-2.1.9/liboctave -I../../octave-2.1.9/src -I../../octave-2.1.9/libcruft/misc -DHAVE_CONFIG_H -mieee-fp -fno-rtti -fno-exceptions -fno-implicit-templates -g -O2 -Wall parse.cc | /usr/share/misc/bison.simple: In function `int yyparse()': | /usr/share/misc/bison.simple:692: virtual memory exhausted | | Note: the path to bison.simple is changed, because I tried to | recreate parse.cc from parse.y, but the error is the same as with | the original parse.cc I can't reproduce this problem with the egcs 1.1a compiler on a Linux i686 system. By watching top, it appears that compiling does take about 23MB, but I don't run out of memory. How much memory and swap space do you have available? jwe