error: memory exhausted or requested size too large

Jaroslav Hajek highegg at gmail.com
Wed Aug 13 03:50:15 CDT 2008


On Tue, Aug 12, 2008 at 4:45 PM, Jim Langston <Jim.Langston at sun.com> wrote:
> Hi Jaroslav,
>
> Here is config.log from my last try. I have tried a lot of different
> variations, this
> last was without any 64bit options. You are correct in that after compiling,
> my
> next step is always to run gmake check, which is this case exits immediately
> on
> the first test.
>
> Also, I tried your suggestion of running ./run-octave, the result was octave
> did not
> start, and my cpu utilization went to 100% and stayed there, never bringing
> up the
> Octave prompt.
>

That's bad. Hmmm, I can't see anything bad in the config file.
Can you try `./run-octave -x'? Perhaps we'll see the command that chokes Octave.
Also, does './run-octave -f' trigger the problem as well?


cheers


-- 
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz


More information about the Help-octave mailing list