X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
X-Authentication-Warning: new-smtp1.ihug.com.au: Host p534-apx1.syd.ihug.com.au [203.173.142.26] claimed to be acceleron
Message-ID: <009801c1807a$8d97dd30$0102a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: <djgpp-workers AT delorie DOT com>, "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
References: <10112030558 DOT AA13822 AT clio DOT rice DOT edu>
Subject: Re: v2.03 refresh ready for review/testing
Date: Sun, 9 Dec 2001 17:26:44 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To: djgpp-workers AT delorie DOT com

Charles,

I have built DJGPP 2.03 refresh on Win 98 box and copied the files onto my
XP box to h:\djgpp. I have noticed a few quirks, like what was ocuring when
we were trying to get the dosexec.c stuff sorted out for Win 2K.

I have been able to re-build all of the packages, except GCC 2.9.5.3. I have
so far seen the following problems:-
    1) Build fail as it cannot pass the argument list to LD.EXE
    2) Out of memory after the build fails
    3) CMD.EXE disappeared once after a build fail when I hit the enter key

I spotted in src\libc\dos\process\dosexec.c that at about line 389 that the
2.04 has the following :-
  /* Work around the W2K NTVDM bug; see dpmiexcp.c for detailed
     explanations.  */
  __maybe_fix_w2k_ntvdm_bug();

The updated 2.03 file does not have this. The function is direct_exec_tail_1
(). Could this be the cause of the problems I haev seen?

Andrew
----- Original Message -----
Subject: v2.03 refresh ready for review/testing


> The following files are available from ftp or http:
>
>   http://clio.rice.edu/djgpp/djdev203.zip  1499 Kb
>   http://clio.rice.edu/djgpp/djlsr203.zip  1501 Kb
>   http://clio.rice.edu/djgpp/djcrx203.zip   620 Kb
>
> My goal here was to only fix bugs - no new features.  When
> possible I tried to use the CVS version of a file (or a section
> of it with bug fixes).  No interface changes were made to the
> library - no .h files changed.  All modules should be completely
> binary compatible with any 2.03 release.  The source is compatible
> with BinUtils 2.8.1 which was the 2.03 vintage (some of the new
> CVS modules are not 2.8.1 compatible).