runtime unpleasantness with setup.exe
Christoph Otto
cotto@ori.org
Thu Jul 26 20:21:00 GMT 2007
The diff breaks on the latest from CVS (as could probably be expected),
but I figured out what the problem was anyway. After adding -DDEBUG to
the compiler flags and looking at the setup.ini on the machines where
setup failed, it turns out a setup.ini left over from a previous
installer was being read instead of mine.
> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com] On Behalf Of Servaas Goossens
> Sent: Tuesday, May 29, 2007 2:31 AM
> To: cygwin-apps@cygwin.com
> Subject: RE: runtime unpleasantness with setup.exe
>
> 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
> generated 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:
>
> *** ini.cc-2.42 Tue Feb 22 11:15:03 2007
> --- ini.cc Tue Feb 20 14:41:56 2007
> ***************
> *** 109,115 ****
> }
> virtual void error(String const &message)const
> {
> ! MessageBox (0, message.c_str(), "Error parsing", 0);
> }
> virtual ~ GuiParseFeedback ()
> {
> --- 109,115 ----
> }
> virtual void error(String const &message)const
> {
> ! MessageBox (0, error_buf, "Error parsing", 0);
> }
> virtual ~ GuiParseFeedback ()
> {
>
> This is probably not the Real Fix, but it helped me a lot.
>
> Servaas
>
> Christoph Otto wrote:
> > Brian Dessent wrote:
> > > Christoph Otto wrote:
> > >
> > >> I'm trying to make an automated cygwin install as part
> of another
> > >> project. Everything works as expected, except on my
> boss's tablet
> > >> (running XP with all updates). There the installer runs
> > into a error
> > >> parsing an ini file (presumably my setup.ini) when using
> the stable
> > >> setup.exe (v2.510.2.2). A screenshot of this error is at
> > >> https://research.ori.org/rft/cygbug/parsing_error.png .
> The only
> > >> changes I made to the setup.ini were to add some Perl
> > packages to the
> > >> Base category so they'd be installed automatically. I
> > also tried to
> > >> build setup.exe from CVS, but using that exectuable gives me a
> > >> runtime error
> > >> (https://research.ori.org/rft/cygbug/runtime_error.png).
> > >> Again, everything (both normal and CVS setup.exe) works
> fine on the
> > >> other two machines I have for testing. The only
> failures happen on
> > >> my boss's tablet. Logs from the install with the stable
> setup.exe
> > >> are in the same directory.
> > >
> > > I think we're going to need more detail to be able to tell you
> > > anything useful. For example, a link to the edited
> setup.ini that
> > > won't parse, or the exact configure/make commands you used
> > to build.
> > >
> > > Brian
> >
> > OK. The configure/make commands were the ones recommended in the
> > readme:
> > https://research.ori.org/rft/cygbug/runconfigure . I've
> also uploaded
> > the setup.ini (https://research.ori.org/rft/cygbug/setup.ini). The
> > only
> >
> > changes from the default are on lines 9291, 9353 and 9371.
> >
> > Christoph
> >
> >
> >
>
>
More information about the Cygwin-apps
mailing list