This is the mail archive of the
mailing list for the Cygwin project.
RE: runtime unpleasantness with setup.exe [please try 2.569]
- From: "Servaas Goossens" <SGoossens at ortec dot nl>
- To: <cygwin-apps at cygwin dot com>
- Date: Wed, 30 May 2007 08:08:30 +0200
- Subject: RE: runtime unpleasantness with setup.exe [please try 2.569]
I tested with an up-to-date release tree and the original setup.ini
(no errors of course).
With a freshly generated setup.ini, containing a syntax error, setup
now shows a list of error messages. Unfortunately, the line
"unrecognized line 8519 (do you have the lastest setup?)" is repeated
10 times, but that's a minor issue to me.
> -----Original Message-----
> From: Brian Dessent [mailto:email@example.com]
> Sent: woensdag 30 mei 2007 06:03
> To: firstname.lastname@example.org
> Subject: Re: runtime unpleasantness with setup.exe [please try 2.569]
> Servaas Goossens wrote:
> > Part of the unpleasantness is caused by the fact that the
> message box
> > doesn't contain any details on why the parse error occured.
> > I had the same problem a few month ago while testing my own
> > setup.ini. I changed one line in ini.cc and got a message box with
> > the error message.
> > This diff is based on ini.cc rev. 2.42, which I used, but rev 2.44
> > is similar:
> I've just reworked a lot of the ini-parsing error handling code. It
> should give you a useful error message containing filename/URL, line
> number, and reason now. Also, as a side effect the progress
> meter works
> during the parsing step, and I've added some code to be more
> robust with
> falling back to setup.ini if the setup.bz2 download fails or the file
> was truncated/corrupt.
> If you were having any issues along the lines of crashes/uninformative
> errors related to parsing, please test 2.569. Thank you.