Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!sunic!ugle.unit.no!sigyn.idt.unit.no!erlingh
From: erlingh@idt.unit.no (Erling Henanger)
Newsgroups: comp.os.minix
Subject: Re: Gnu C (68k) failed, WHY???
Message-ID: <1991Feb18.171211.8560@ugle.unit.no>
Date: 18 Feb 91 17:12:11 GMT
References: <44909@nigel.ee.udel.edu>
Sender: news@ugle.unit.no
Reply-To: erlingh@idt.unit.no (Erling Henanger)
Organization: Div. of CS & Telematics, Norwegian Institute of Technology
Lines: 8

I think a start would be to check what all the binaries are 'chmem'ed to. If it adds up to more ram than you've got, then you'll get that message.
(That is: ram_available - mem(gcc) - mem(gcc-cc1) - mem(shell) < 0 )
Try chmem -50000 gcc-cc1 until it works...
-- 
       _______    _____  	 o	     ____       Erling Henanger
      /___       /____/ /       /   /|  /   /           Norwegian institute
     /          /\     /       /   / | /   |   ___      of technology. (NTH)
    ------     /  \   /____   /   /  |/     \____| o    Atari Lives !