🚀 go-pugleaf

Michael Strauch (strauch@emmy.mathematik.uni-dortmund.de) wrote:
: marghidan@marghidan (Eduard Marghidan) writes:

: >        Whenever compiling programs with GCC 2.5.7 from DJGPP ver 1.11m1,
: >the disk accesses almost continously. This is on a 20 MB RAM, 486/33 machine.
: >It seems that GCC wants to write everything to temp files while compiling 
: >the
: >object and while linking. Any way I can force it to use RAM and not the disk?
: >It also fails with QDPMI (QEMM ver 7.03) so it will only use VCPI.
: >I suppose I can substitute a RAM drive, but that's a kludge.

: Which version of "make" do you use? I had the same problem because I used
: the "make" program from Borland's C++ compiler. This "make" installs a DPMI
: handler which takes all the extended memory for itself. You can get around this
: error by using "maker", the real mode version of Borland's make, or better
: one of the public domain/shareware "make" programs like "ndmake".

: - Michael -
: strauch@emmy.mathematik.uni-dortmund.de

I use Quarterdeck's QMAKE, which I believe is real mode. I'm not sure
what tells GCC to go to disk for virtual memory. I'll have to take a look
at what happens without QMAKE, and how much RAM is actually being used.
Thanks for the pointer.
Eduard

--
/********************************************
 * Eduard Marghidan   88 
 * eduard@netcom.com  88
 *******************************************/