Date:	Mon, 6 Nov 2000 06:27:39 +0600 (LKT)
From:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender:	kalum AT spartacus DOT grendel DOT net
To:	Bill Currie <bill AT taniwha DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: Three years is too long...
In-Reply-To:	<20001105154922.A13421@taniwha.org>
Message-ID:	<Pine.LNX.4.21.0011060621350.20346-100000@spartacus.grendel.net>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On  Sun, 5 Nov 2000, Bill Currie commented thusly,

> Now for my question (with lead-up): I'm building one of my old djgpp libs on a
> 486-100 with 16M ram and it's taking longer than it used to on my old 386-33 w
> 8M. I'm using Caldera OpenDOS 7.1 (yes, the free release from 4 or 5 years
> ago) and while I did once have it tweaked to the max, I can't remember how to
> drive the thing optimally for djgpp (well, at all, really:). I believe I'm
> probably paging my machine to death.

Do you have a disk cache with write caching enabled running. If you do not
have one please do run one as it will vastly improve the speed of gcc.

You can try a 4 mb cache with write caching enabled, for example I use
smartdrv 4000 c+ 

which setsup smartdrive with a 4 mb cache and enables write caching for
drive c.

> Are there any tools available in djgpp for reporting things like physical
> memory, any recommendations for settings, etc etc.

go32-v2 reports on memory. The DJGPP FAQ is the other "tool" I know that
gives info about what settings to use, please check the section on slow
compilation etc.

Best Wishes,
Grendel


-- 
.---------------------.---------------------.----{)--.
| /"__ ._ _  _  _| _ |`-.grendel AT lintux DOT cx.-'(]__/|| |
| \__/ | (-'| |(_|(-'l_ `-===============-' [_]  .-: |
`--------------------------------------------/|\/| |-'

"Linux was made by foreign terrorists to take money from true US companies
like Microsoft." - Some AOL'er.

- Raw text -