This is the mail archive of the
mailing list for the Cygwin project.
Re: setup problems when updating cygwin1.dll
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Lapo Luchini <lapo dot luchini at gmail dot com>
- Cc: cygwin-apps at cygwin dot com
- Date: Sun, 26 Mar 2006 14:33:36 -0500 (EST)
- Subject: Re: setup problems when updating cygwin1.dll
- References: <4426656F.firstname.lastname@example.org>
- Reply-to: cygwin-apps at cygwin dot com
On Sun, 26 Mar 2006, Lapo Luchini wrote:
> It correctly says "you have to reboot, cygwin could not work correctly
> until you reboot"... but then works "not correctly" a few seconds
> later, during postinstall scripts ;-)
> (lots of "entry point not found")
Hmm, one way of addressing this would be to also schedule the postinstall
scripts to run on reboot, rather than running them at that point.
> I don't think this can easily avoided, but at least the message could
> be changed to warn the user about it (maybe just in the case it can be
> needed, i.e. when cygwin1.dll changes).
FWIW, any DLL change can prompt such behavior... It's just more common
> Ah, I also had a local package aspell-it whose .tar.bz2 was
> "truncated" as far as "tar" told, but that setup.exe extracted in an
> "infinite file" (I killed it when it had already extracted 840MB out
> of a 33MB file).
Hmm, that's a completely separate issue. If you still have that
"truncated" file, it would be useful in figuring out whether setup's tar
algorithm has a bug. Does the command-line tar have the same problem?
|\ _,,,---,,_ 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"