Date: Tue, 23 Sep 1997 13:11:37 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andrew Ellem <krand AT ican DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Allegro WIP (virtual memory exausted)
In-Reply-To: <606l0a$h72$1@news1.tor.acc.ca>
Message-ID: <Pine.SUN.3.91.970923131057.14928N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 22 Sep 1997, Andrew Ellem wrote:

> gcc -I. -Isrc -Isrc/djgpp -Iobj/djgpp -Wall -W -Werror -m486 -O3 -ffast-math 
> -fomit-frame-pointer -o obj/djgpp/colblend.o -c src/colblend.c
> src/colblend.c: In function `blend16_73':
> src/colblend.c:227: virtual memory exhausted
> make.exe: *** [obj/djgpp/colblend.o] Error 1

Did it ever occured to you that GCC might be telling the truth, and
that it *really* has run out of virtual memory?  Virtual memory
doesn't mean unlimited memory, you know ;-)

What does go32-v2 print when run with no arguments in the same
environment (i.e., in the same DOS box on Windows 95) where you tried
to compile Allegro?