Igor Peshansky wrote:
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.
FWIW, any DLL change can prompt such behavior... It's just more common
with cygwin1.dll.
Mhh... I guess just adding a
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