Date:	Tue, 5 Oct 1999 16:10:57 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	jcditz AT tardis DOT svsu DOT edu
cc:	djgpp AT delorie DOT com
Subject:	Re: Allegro Make Time
In-Reply-To:	<7tcajs$fqc$1@nnrp1.deja.com>
Message-ID:	<Pine.SUN.3.91.991005160724.4995F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 5 Oct 1999 jcditz AT tardis DOT svsu DOT edu wrote:

> I have DJGPP installed on a 486 SX 33 with 8 MB of RAM and about 150 MB
> of free HDD space (built the computer from spare partS). I tried to
> make Allegro on it though...
> And its going at incredibly slow speeds. Its been running for 30+ hours
> and its nowhere near done yet.
> bmp.c alone took about 10 hours to get through, thats only a 15 KB
> file!

First, be sure to read section 3.9 of the DJGPP FAQ list, and set up your 
system in an optimal way, as per the advice there.  I'm guessing that 
this is your problem.

If that doesn't help, one possibility is that Make (and/or the compiler) 
is issuing floating-point instructions, which run extremely slow on 
486SX due to emulation.  To see if this is indeed so, point the emu387 
environment variable to a non-existent file, and try to build Allegro.  
If any program that participates in the build issues FP instructions, the 
build process will crash with SIGFPE.

- Raw text -