Date: Sun, 27 Aug 1995 08:44:21 +0200 (IST) From: Eli Zaretskii To: Roland Schregle Cc: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Re: Thrashing On 26 Aug 1995, Roland Schregle wrote: > I recently upgraded from gcc version 2.6.0 to 2.6.3. > Now I regret it already. > No changes were made to config.sys or autoexec.bat (under DOS 5.0), and > gcc simply thrashes on even the simplest C++ programs... and compiles into > eternity without any noticeable progress. Well, you *really* should regret that you didn't look into the DJGPP FAQ list (available as faq102.zip from the same place you get DJGPP), because it explains how to overcome this: 2.8 Q: How do I configure my system to get optimal performance under DJGPP? A: That depends on the amount of RAM you have installed in your machine. Below are some guidelines to help you. 1) If you have 4 MBytes or less RAM installed: * Don't use *any* memory manager. * Remove any TSR and device driver you don't absolutely need (like SETVER.EXE, HIMEM.SYS) from your CONFIG.SYS and AUTOEXEC.BAT. * Get a disk cache which works from conventional memory and configure it to 256K size at most, or don't use a cache at all. * Do *not* install RAM disk; point you TMPDIR environment variable to a directory on your hard disk. * Stubedit gcc.exe and make.exe and change the "Maximum amount of virtual memory to keep when spawning" to zero. With this configuration, GCC will still run out of free physical RAM and page when compiling large C programs and most C++ programs. Also, you most probably won't be able to run recursive Makefiles. Plan to buy more RAM as soon as you can. The last recommendation about stubediting should do the trick for you. If it does not, please post your system configuration and what go32 prints when called with no arguments.