Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!usc!rpi!zaphod.mps.ohio-state.edu!rphroy!hobbes.cs.gmr.com!tkacik
From: tkacik@hobbes.cs.gmr.com (Tom Tkacik CS/50)
Newsgroups: comp.sys.3b1
Subject: Re: Virtual memory and exhaustion
Keywords: virtual-memory exhaustion poop
Message-ID: <57142@rphroy.UUCP>
Date: 27 Jun 91 13:27:23 GMT
References: <137@morwyn.UUCP>
Sender: news@rphroy.UUCP
Reply-To: tkacik@hobbes.cs.gmr.com (Tom Tkacik CS/50)
Organization: G.M. Research Labs, Warren, MI
Lines: 29
Nntp-Posting-Host: hobbes.cs.gmr.com

In article <137@morwyn.UUCP>, forrie@morwyn.UUCP (Forrie Aldrich) writes:
|> I've been noticing this problem more and more recently as I attempt
|> to compile things.  And the problem is consistently saying :
|> 
|> 	"Virtual Memory exhausted ..."

Have you been compiling with gcc?  That is a gcc error message.

|> I have recently had this problem when trying to compile the GNU
|> fileutils programs.  This is version 2.01 I am compiling... yet
|> the previous version I had (1.14?) I had absolutely no problem.
|> 
|> Also, this machine doesn't like to compile PERL either... so I had
|> to snarf the executables from elsewhere.

Gcc can take lots of virtual memory to compile large files,
more than a 3b1 has.
I know that in perl there are two files, eval.c and toke.c, that cannot
be compiled with gcc on a 3b1.  I have not tried compiling the fileutils
programs, but suspect you may have the same problem with them.

I always simply fall back on cc for those files that gcc can't handle.

Virtual memory is limited to 2.5Meg independent of RAM and disk size.
--
Tom Tkacik
GM Research Labs
tkacik@hobbes.cs.gmr.com
tkacik@kyzyl.mi.org