Message-ID: <002c01c202f4$1cdf0990$0102a8c0@acceleron> From: "Andrew Cottrell" To: References: <10205240339 DOT AA17287 AT clio DOT rice DOT edu> Subject: Re: refresh++ Date: Fri, 24 May 2002 17:24:22 +1000 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 > Plans are to refresh with the following files: > > readme.1st win2k/xp doc updates > djdev203.(ver,dsm) update version and misc dsm fixes > djgpp.env env variable updates > string.h gcc 3.x fix > djtypes.h gcc 3.x fix > > No plans to try any binary updates. Is that what everyone remembered? Sounds okay, but until the LIBC code is patched to build with GCC 3.1 you may want to add a readme specific for GCC 3.1 that says something like:- The current LIBC needs to have a number of funtion calls changed due to stricter checking and some type changes that are included in GCC 3.1 I should be able to produce a series of patches this weekend. So far the following files are affected (ran out of time to finish this the other day):- fprintf.c fscanf.c printf.c remove.c ...... more to come Regards, Andrew