From: pavenis AT lanet DOT lv
To: "Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>, djgpp AT delorie DOT com
Date: Tue, 9 May 2000 14:48:49 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Compile gcc-2.952 on Windows NT
Message-ID: <39182551.23690.37F34D@localhost>
In-reply-to: <8f8o98$c2i$1@sunsite.icm.edu.pl>
X-mailer: Pegasus Mail for Win32 (v3.12c)
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
Precedence: bulk

On 9 May 2000, at 12:11, Wojciech Galazka wrote:

> 
> Eli Zaretskii wrote
> >
> >But if you close the DOS box and then open another and say "make" again,
> >won't the build process continue from the same point where the previous
> >one failed?
> 
> This is indeed possible I went up to compiling libio & libgpp stage and then
> stooped
> 
> 

Once more. Seems that there is one difference in misbehaving of 
Win9X and WinNT 4.0 DPMI server:

	Under Win9X if I return to command prompt (and quit all DJGPP 
	applications in that DOS session) DPMI server seems to be reset
	so one can split large task into parts as I did with building 
	gcc-2.95.2 for DJGPP which are invoked from BAT file.

	Under WinNT system I tested it seems that such reset doesn't
	happen and as result one have to quit DOS prompt to continue.
	So suggestion:
		try each step of building gcc from build.bat but restart DOS 
		session under each step.

Andris

PS. Strange, but some time ago I gave test program to my colegue and 
I didn't saw DPMI descriptor leak on his WinNT 4.0 machine. But then
I had similar behaviour also for DOSEMU