Xref: utzoo comp.sys.atari.st.tech:1730 comp.sys.atari.st:36361
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!ai-lab!opal!db0tui11!gerloff
From: GERLOFF@tubvm.cs.tu-berlin.de (Olaf Gerloff)
Newsgroups: comp.sys.atari.st.tech,comp.sys.atari.st
Subject: Re: GCC: Virtual memory exhausted error?
Message-ID: <91079.134917GERLOFF@DB0TUI11.BITNET>
Date: 20 Mar 91 11:49:17 GMT
References: <0bsiSby00VADAIpl4O@andrew.cmu.edu>
Organization: Technical University Berlin
Lines: 24

In article <0bsiSby00VADAIpl4O@andrew.cmu.edu>, es2a+@andrew.cmu.edu (Eric
Stuyvesant) says:
>
>I'm running gcc from RAMdisk on my 4 Mb system, and am playing a
>balancing game between disk space and memory.  I have been getting an
>error from GCC, namely "Virtual memory exhausted."  Does this really
>mean "disk space exhausted," as it seems to imply, or does it mean "not
>enough memory?"  It doesn't seem to matter which version of gcc I use,
>be it 1.37 or 1.39.
>

It means that gcc hasn't enough memory to work. He says virtual memory, because
gcc was first designed for UNIX, where you have virtual memory because of
paging and/or swaping.

Greetings, Olaf
-------
*******************************************************************************
* Olaf Gerloff                      * Internet: GERLOFF@tubvm.cs.tu-berlin.de *
* Technical University Berlin (FRG) * BITNET  : GERLOFF@DB0TUI11              *
*******************************************************************************
*               Impossible things will be executed immediately,               *
*                       miracles take a little longer!                        *
*******************************************************************************