Date: Tue, 3 Sep 1996 17:18:50 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: djgpp AT delorie DOT com
Cc: herberho AT mango DOT biochem DOT mpg DOT de
Subject: Re: still the dr dos problem...
In-Reply-To: <50h1m7$5em7@sat.ipp-garching.mpg.de>
Message-Id: <Pine.SUN.3.91.960903170826.26423A-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 3 Sep 1996, Christoph Herberhold wrote:

> Thanks for all attempts to help me! But it still doesn't compile..

OK, then add -v to the GCC command line and post everything that it 
prints.  The best way to do that is to use the `redir' program, like so:

	redir -o gcc.out -eo gcc -v ...

(put all the rest of the GCC command line instead of the dots), then post 
the contents of the file `gcc.out'.

#=
ECHO Meldung
DJDIR=%:/>DJGPP%
[snip]
> [info]
> INFOPATH=%/>;INFOPATH%%DJDIR%/info
> 

Remove that ``ECHO Meldung'' line and the trailing ^Z!

> output of go32-v2go32/v2 version 2.0 built Jan 23 1996 22:03:02
> Usage: go32 coff-image [args]
> Rename this to go32.exe only if you need a go32 that can run v2 binaries as
>  well as v1 binaries (old makefiles).  Put ahead of the old go32 in your PATH.
> DPMI memory available: 236 Kb
                         ^^^^^^
Please read section 3.9a of the DJGPP FAQ list (available as 
v2/faq201b.zip from the same place you get DJGPP).  It explains how to 
set up CWSDPMI so that you will have more DPMI memory available to DJGPP 
programs, even on memory-starved machines such as yours.

(The last two recommendations are NOT the causes of your compilation 
problems, but they might bite you down the road.)