Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions Subject: Re: Virtual memory problem Date: 8 Jul 1993 20:34:16 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 24 Message-ID: <21ihv6$5t4@hrd769.brooks.af.mil> References: <21i13cINN229@srvr1.engin.umich.edu> <D> <1993Jul9.001503.8706@news.arc.nasa.gov> NNTP-Posting-Host: hrd769.brooks.af.mil In article <1993Jul9.001503.8706@news.arc.nasa.gov> root@wanderer.nsi.nasa.gov (Michael C. Newell) writes: }In article <21i13cINN229@srvr1.engin.umich.edu>, cobb@cheddar.engin.umich.edu (Paul Cobb) writes: }|> }|> Okay, I'm going nuts now. I'm using the straight 386bsd 0.1 and trying to compile my code. It's giving me a running out of virtual memory error during }|> compile on some of the routines. However there is 20 meg of swap space in the }|> b partition. Is there a problem with the gcc compiler in straight 386bsd 0.1 }|> or something. There is just no way it should use up 20 megs of virtual memory }|> to compile one routine. Any help would be appreciated. }|> } }Another FAQ candidate?? I ran into this too; I got about 10 Email messages }telling me to check out the csh "limit" command. } } Too late :-) It is already in there. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX