delorie.com/archives/browse.cgi | search |
Message-ID: | <001601c2c505$d2decb80$0100a8c0@acp42g> |
From: | "Andrew Cottrell" <acottrel AT ihug DOT com DOT au> |
To: | <djgpp-workers AT delorie DOT com> |
Subject: | CVS get for next CLio update - okay or wait? |
Date: | Sun, 26 Jan 2003 17:40:01 +1100 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook Express 6.00.2800.1106 |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1106 |
Reply-To: | djgpp-workers AT delorie DOT com |
I just did a CVS get (4:25 AM Sunday 26th Jan UTC time, 5:25 PM OZ time) and if no one indicates otherwise I will be using this to build the next 2.04 update for clio if I don't find any show stoppers. Anyone know of any show stoppers in the CVS code where you would advise against doing a build and leting people use it? Once this release is done I will take a break if possible from doing any updates until I sort out the following issues:- 1) Get a Rhide snapshot built with lastest Rhide, TV and CVS code. I have done this in early 2002, but allot of water has been under the bridge since then so this may take a while. 2) Check out all work arrounds that I have done in order to do a complete build. This includes sorting out grep 2.5.1 build process and some other problems. If anyone wants to help out I will be uploading my 2 build batch files in the next clio update so people can see what the workarrounds I have used. Thanks, Andrew
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |