The postinstall scripts for 1.5.3 rely on executing commands that might have dependencies on the cygwin1.dll that has not been installed yet! If you are installing and cygwin1.dll is loaded then setup will not be able to put the new cygwin1.dll in place. Instead it puts it as cygwin1.dll.new and arranges for it to be put into place next reboot. However this does not stop the postinstall scripts from running. When a postinstall script runs it may execute say grep, but the new grep makes calls to a new or renamed function expecting to find it in the new cygwin1.dll. This fails and a dialog box is put up.
Now the situation is understandable. The question is: Did the postinstall script accomplish what it needed? After I reboot can I be assured that the "failed" postinstall script did enough of what it needed to do? Or should I re-execute (all) postinstall scripts?
===
Obligatory witty line: Mental Floss prevents Moral Decay.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
