Date:	Wed, 16 Sep 1998 12:18:05 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	jtgalkowski AT alum DOT mit DOT edu
cc:	djgpp AT delorie DOT com
Subject:	Re: Recently installed version of DJGPP's gcc hangs
In-Reply-To:	<6tm69l$aug$1@nnrp1.dejanews.com>
Message-ID:	<Pine.SUN.3.91.980916121747.5874P-100000@is>
MIME-Version:	1.0

On Tue, 15 Sep 1998 jtgalkowski AT alum DOT mit DOT edu wrote:

> gcc is happy with about 5 of 27 of its pieces -- no error messages
> in any of them.  When it gets to the 6th, the compilation seems
> to take forever.  There is disk activity.  I issued the SIGINT
> using Ctrl-Break and the snapshot came back saying it was in a page
> fault.  The Error=6.  I'm not sure if that happened because of the
> Ctrl-Break going awry or it is the underlying problem.
> 
> I will run this again tonight, letting it go longer.

Please do let it run longer, because it's quite possible that the
compiler was paging due to insufficient memory (6MB free is not always
enough, especially for large sources and some pathological cases).
The disk activity seems to indicate that paging is indeed happening,
and this would usually considerably slow down the compiler, so be
patient.

If the compiler doesn't seem to finish even if you leave it to run for
hours, please tell more:

       1) what package are you trying to compile;
       2) do you compile it using Make or with some batch file/manual
	  procedure;
       3) details about the source file where it gets stuck: size,
	  source language, complexity;
       4) the exact output of go2-v2.exe when run without arguments.

If you don't have a disk cache installed, I'd suggest to install one
(e.g., SmartDrv that comes with DOS); it can speed out things
tremendously.  See section 3.9 of the DJGPP FAQ list (v2/faq210b.zip
from the same place you get DJGPP) for other tips on system
configuration.

> Also, while I've run gcc and gdb and bash many times before, it
> was always on a Solaris or Ultra or Alpha.  Not quite sure what
> to expect in this DOS environment.

Expect them to work almost 100% like they would on Unix.  The
differences in GDB functionality are described in section 12.1 of the
FAQ.  Bash has a README.dos file that explains some DJGPP-specific
features.

>  (1) Needs to be installed in something like an autoexec.bat or
>      the makefile.bat?
> 
>  (2) Needs to be run once per session however?
> 
>  (3) Just interrogates the status of something which gcc and the
>      other DJGPP tools set up for themselves?
> 
>  (4) I so misunderstand that these questions are off the mark.

None of the above ;-).  go2-v2 is a diagnostic tool, and is also used
to run raw COFF executables in some rare circumstances.  Section 22.12
in the FAQ has more details.

- Raw text -