Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Setup failures over the last few days
Date: Fri, 10 May 2002 16:23:49 -0400
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E40EFBD@ex02.idirect.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Harig, Mark A." <maharig AT idirect DOT net>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>,
   "Cygwin" <cygwin AT sources DOT redhat DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4AKO8R13231

This fixes the problem that I saw with setup.exe, version 2.194.2.26,
that is, parsing errors in setup.ini and referring to line numbers that
were not in the file.  Please ignore my message in the 'setup continuing
difficulties' thread.

Thanks for the quick fix!

> -----Original Message-----
> From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au]
> Sent: Friday, May 10, 2002 7:24 AM
> To: Cygwin
> Subject: Setup failures over the last few days
> 
> 
> Short answer: use
> http://www.cygwin.com/setup-snapshots/setup-20020510.exe.
> 
> Long answer: The new MD5 rule + the number of packages which increased
> recently caused a yacc parsing failure. This has been corrected in CVS
> for the pre-release version and for HEAD.
> 
> As I've seen no bug reports on the UPX support, I've started 
> compressing
> setup with UPX as a matter of routine.
> 
> Please, try the setup linked above, and if you have any errors let me
> know. AFAICT though, it should be ready for widespread use now.
> 
> I'm not planning on updating the current setup, as 
> 1) It was about to be obsoleted anyway and
> 2) Users will still have the stack failure/crash anyway, so they will
> have to update manually regardless.
> 
> Rob
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/