X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
From:	"Jakub" <jrat AT newitech DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gcc finishes in the middle of compilation
Date:	Thu, 14 Mar 2002 13:49:59 +0100
Organization:	tp.internet - http://www.tpi.pl/
Lines:	32
Message-ID:	<a6q67m$18r$1@news.tpi.pl>
References:	<a6ofps$kmv$1 AT news DOT tpi DOT pl> <3c8fef7e DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host:	80.48.69.20
X-Trace:	news.tpi.pl 1016110134 1307 80.48.69.20 (14 Mar 2002 12:48:54 GMT)
X-Complaints-To:	usenet AT tpi DOT pl
NNTP-Posting-Date:	Thu, 14 Mar 2002 12:48:54 +0000 (UTC)
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MSMail-Priority:	Normal
X-Priority:	3
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Thanks for help.
In fact it looks like ntvdm bug described on the djgpp page. I'll check it
on my W2K this evening.
But: I've got the same problem on NT4SP6. The only difference is that
produced files are bit shorter - the cc1.exe terminates earlier.
I tried NT4 with djgpp 2.952, 2.953, 3.04 and it's always the same (files
dates are ok). In the attachement you will find source files (they are bit
strange because they are produced automatically by other software but I can
assure that it compiles on Linux).
The patch NTVDMPAT.EXE obviously doesn't work with NT4.
Have you got any ideas about that?
I appreciate any help.
Jakub

> > I've got W2K with gcc 2.952. When I try to compile one source file:
>
> You need to make sure you have .EXE files dated in December 2001 or
> later.  In particular, make sure bnu2112b.zip, gcc2953b.zip, djdev203.zip
> are the refreshed versions.  Check the date and size of these on
> Simtel and get newer versions if needed.
>
> Explanation:
>   http://clio.rice.edu/djgpp/win2k/main_203.htm
>
> > gcc finishes abnormally without any error message in the middle of
> > compilation. Log finishes like this:
>
> Sounds like the ntvdm bug in win2k - you can patch ntvdm to work
> around this bug but you'll find more in Win2K.  Refresh to make your
> life easier.

- Raw text -