This is the mail archive of the
mailing list for the Cygwin project.
Re: [Q] About halting problems at installation of cygwin
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Eric Blake <ebb9 at byu dot net>
- Cc: cygwin at cygwin dot com
- Date: Thu, 27 Jul 2006 09:57:12 -0400 (EDT)
- Subject: Re: [Q] About halting problems at installation of cygwin
- References: <OEEKLGEMJOIGCCPNCJPIOEAKCCAA.email@example.com> <44C8B43A.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Thu, 27 Jul 2006, Eric Blake wrote:
> In your setup.log.full, you had lots of these messages:
> > 2006/07/25 17:12:47 io_stream_cygfile: fopen failed 2 No such file or directory
> My recollection is that this has been improved in a recent snapshot of
> setup.exe - who is in charge of releasing the next setup.exe version?
> > 2006/07/25 17:32:58 running: C:\Apps\cygwin\bin\bash.exe -c /etc/postinstall/aalib.sh
> > /usr/bin/bash: /etc/postinstall/aalib.sh: /bin/sh: bad interpreter: No such file or directory
> > 2006/07/25 17:33:01 running: C:\Apps\cygwin\bin\bash.exe -c /etc/postinstall/apache.sh
> > /usr/bin/bash: /etc/postinstall/apache.sh: /bin/sh: bad interpreter: No such file or directory
> > 2006/07/25 17:33:01 running: C:\Apps\cygwin\bin\bash.exe -c /etc/postinstall/apache2.sh
> > /usr/bin/bash: /etc/postinstall/apache2.sh: /bin/sh: bad interpreter: No such file or directory
> > 2006/07/25 17:33:01 running: C:\Apps\cygwin\bin\bash.exe -c /etc/postinstall/00ash.sh
> > 2006/07/25 17:33:02 abnormal exit: exit code=0
> Hmm - when doing a global install of every single cygwin package (which
> usually isn't recommended, but is what you did),
Frankly, one reason it wasn't recommended was probably the fact that
postinstall scripts wouldn't run correctly on a full install, so you'd end
up with a broken one. Read on.
> it looks like the setup.exe sort method of postinstall scripts is
> alphabetical by package name, not by postinstall name. I wish we could
> get a setup.exe that sorted by dependency order instead.
Setup *does* sort in dependency order, but there was a bug in script
detection that caused setup to fail to associate the scripts with their
packages, so all scripts were run in the catch-all clause, which sorted
alphabetically. This has also been improved in the recent setup
snapshots. I wish we could get a setup.exe release... Brian?
|\ _,,,---,,_ email@example.com | firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html