From bug-octave-request at bevo dot che dot wisc dot edu Wed Nov 26 00:31:53 1997 Subject: Can not compile octave on bsd : "virtual memory exhausted" From: "John W. Eaton" To: Vincent Cautaerts Cc: bug-octave at bevo dot che dot wisc dot edu Date: Wed, 26 Nov 1997 00:32:03 -0600 On 25-Nov-1997, Vincent Cautaerts wrote: | Bug report for Octave 2.0.9 configured for i386-unknown-freebsd2.2.5 | | Trying to compile octave on a bsd machine, the compilation did fail, | | Here is the end of the output from "make": | ------- | make[2]: Entering directory `/usr/local/work/octave/octave-2.0.9/src' | c++ -c -I. -I.. -I../liboctave -I../src -I../glob -I../libcruft/misc -DHAVE_CONFIG_H -fno-implicit-templates -mieee-fp -g -O2 -Wall builtins.cc | builtins.cc: In function `(static destructors for builtins.cc)': | builtins.cc:680: virtual memory exhausted | make[2]: *** [builtins.o] Error 1 | make[2]: Leaving directory `/usr/local/work/octave/octave-2.0.9/src' | make[1]: *** [src] Error 2 | make[1]: Leaving directory `/usr/local/work/octave/octave-2.0.9' | make: *** [all] Error 2 | ------ | By rerunning make, I could see that suddenly the memory usage of make | (actually cc1) jumps, going suddenly from less than 1Mb to 20Mb (in | about 5 seconds on this Pentium 300MHz) Despite the 128Mb of RAM, | this message does appear. | | Shortly before the error, here is a line of output of "top": | | PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND | 9063 vincent 88 2 14864K 14868K RUN 0:07 56.22% 26.89% cc1plus | | Do you have any idea of why this happens ?? Bug in gcc ? When I use gcc 2.7.2 to compile builtins.cc on a Linux system, gcc grows to about 16MB, but that's it. What else are you running? How much free memory is really available on your system? | [BTW: any idea about when the next (stable) release will come?] Of Octave? I'm not sure, but I have been making test releases of 2.0.10 lately. They are available on ftp.che.wisc.edu in the directory /pub/octave/test-releases. jwe