* runtime unpleasantness with setup.exe [not found] <1178571662.14745.ezmlm@cygwin.com> @ 2007-05-07 21:35 ` Christoph Otto 2007-05-07 21:53 ` Brian Dessent 0 siblings, 1 reply; 7+ messages in thread From: Christoph Otto @ 2007-05-07 21:35 UTC (permalink / raw) To: cygwin-apps 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. Christoph ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: runtime unpleasantness with setup.exe 2007-05-07 21:35 ` runtime unpleasantness with setup.exe Christoph Otto @ 2007-05-07 21:53 ` Brian Dessent 2007-05-07 22:39 ` Christoph Otto 0 siblings, 1 reply; 7+ messages in thread From: Brian Dessent @ 2007-05-07 21:53 UTC (permalink / raw) To: cygwin-apps 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: runtime unpleasantness with setup.exe 2007-05-07 21:53 ` Brian Dessent @ 2007-05-07 22:39 ` Christoph Otto 2007-05-29 9:28 ` Servaas Goossens 0 siblings, 1 reply; 7+ messages in thread From: Christoph Otto @ 2007-05-07 22:39 UTC (permalink / raw) To: cygwin-apps 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: runtime unpleasantness with setup.exe 2007-05-07 22:39 ` Christoph Otto @ 2007-05-29 9:28 ` Servaas Goossens 2007-05-30 4:01 ` runtime unpleasantness with setup.exe [please try 2.569] Brian Dessent 2007-07-26 20:21 ` runtime unpleasantness with setup.exe Christoph Otto 0 siblings, 2 replies; 7+ messages in thread From: Servaas Goossens @ 2007-05-29 9:28 UTC (permalink / raw) To: cygwin-apps 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 > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: runtime unpleasantness with setup.exe [please try 2.569] 2007-05-29 9:28 ` Servaas Goossens @ 2007-05-30 4:01 ` Brian Dessent 2007-05-30 6:08 ` Servaas Goossens 2007-07-26 20:21 ` runtime unpleasantness with setup.exe Christoph Otto 1 sibling, 1 reply; 7+ messages in thread From: Brian Dessent @ 2007-05-30 4:01 UTC (permalink / raw) To: cygwin-apps 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 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: 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. Brian ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: runtime unpleasantness with setup.exe [please try 2.569] 2007-05-30 4:01 ` runtime unpleasantness with setup.exe [please try 2.569] Brian Dessent @ 2007-05-30 6:08 ` Servaas Goossens 0 siblings, 0 replies; 7+ messages in thread From: Servaas Goossens @ 2007-05-30 6:08 UTC (permalink / raw) To: cygwin-apps Looks good. 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. Servaas. > -----Original Message----- > From: Brian Dessent [mailto:brian@dessent.net] > Sent: woensdag 30 mei 2007 06:03 > To: cygwin-apps@cygwin.com > 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 > 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: > > 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. > > Brian > ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: runtime unpleasantness with setup.exe 2007-05-29 9:28 ` Servaas Goossens 2007-05-30 4:01 ` runtime unpleasantness with setup.exe [please try 2.569] Brian Dessent @ 2007-07-26 20:21 ` Christoph Otto 1 sibling, 0 replies; 7+ messages in thread From: Christoph Otto @ 2007-07-26 20:21 UTC (permalink / raw) To: cygwin-apps 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 > > > > > > > > ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-07-26 20:21 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <1178571662.14745.ezmlm@cygwin.com> 2007-05-07 21:35 ` runtime unpleasantness with setup.exe Christoph Otto 2007-05-07 21:53 ` Brian Dessent 2007-05-07 22:39 ` Christoph Otto 2007-05-29 9:28 ` Servaas Goossens 2007-05-30 4:01 ` runtime unpleasantness with setup.exe [please try 2.569] Brian Dessent 2007-05-30 6:08 ` Servaas Goossens 2007-07-26 20:21 ` runtime unpleasantness with setup.exe Christoph Otto
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).