Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <434A5D0A.9070608@byu.net> Date: Mon, 10 Oct 2005 06:22:34 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Norbert Harendt CC: cygwin AT cygwin DOT com Subject: Re: cygwins setup hangs in installation References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Norbert Harendt on 10/10/2005 2:33 AM: > I downloaded the updated packages for install from Internet (with locally > keeping the files) using cygwins setup.exe under W2K prof. > All is running fine, packages are downloaded as they should, installation > takes place, untill the notice of a pre- or postinstall appears in the > setup window. Then the setup seems to hang, nothing happens. > > Since i wanted to stop the installation i found the process sh.exe in > Windows Taskmanager showing no activity. After killing sh.exe the setup > continues. But every time a postinstall procedure is shown, the taskmanager > shows sh.exe with no activity (CPU-load =0). Waiting for the process to > finish doesn't help, so i killed every sh.exe. The point of postinstall scripts is that sh.exe runs something else. sh will show up as no activity, because it is waiting on the child process, which IS doing something. If you abort postinstall scripts, then your installation WILL be broken. You can check /etc/postinstall/, and see what scripts have not yet run (suffix of .sh instead of .sh.done). You probably also want to rerun setup.exe, and let the postinstall scripts have a chance to run for a while longer before claiming they have hung. Your bigger problem is that you have a third-party conflict. Only one version of cygwin1.dll is found on your path (good), and it looks like q:\progs.win\cygwin\bin is your cygwin version which is masking c:\bin. However, your setup will have problems if the wrong version of these programs is being invoked. > > Found: Q:\progs.win\cygwin\bin\awk.exe > Found: Q:\progs.win\cygwin\bin\bash.exe > Found: c:\bin\bash.exe > Warning: Q:\progs.win\cygwin\bin\bash.exe hides c:\bin\bash.exe > Found: \bin\bash.exe > Warning: Q:\progs.win\cygwin\bin\bash.exe hides \bin\bash.exe > Found: Q:\progs.win\cygwin\bin\cat.exe > Found: c:\bin\cat.exe > Warning: Q:\progs.win\cygwin\bin\cat.exe hides c:\bin\cat.exe > Found: c:\Programme\VisiQuest\bin\win32vs7\cat.exe > Warning: Q:\progs.win\cygwin\bin\cat.exe hides > c:\Programme\VisiQuest\bin\win32vs7\cat.exe > Found: \bin\cat.exe > Warning: Q:\progs.win\cygwin\bin\cat.exe hides \bin\cat.exe > Found: Q:\progs.win\cygwin\bin\cp.exe > Found: c:\bin\cp.exe > Warning: Q:\progs.win\cygwin\bin\cp.exe hides c:\bin\cp.exe > Found: \bin\cp.exe > Warning: Q:\progs.win\cygwin\bin\cp.exe hides \bin\cp.exe > Found: Q:\progs.win\cygwin\bin\cpp.exe > Found: Q:\progs.win\cygwin\bin\find.exe > Found: c:\bin\find.exe > Warning: Q:\progs.win\cygwin\bin\find.exe hides c:\bin\find.exe > Found: \bin\find.exe > Warning: Q:\progs.win\cygwin\bin\find.exe hides \bin\find.exe > Found: Q:\progs.win\cygwin\bin\gcc.exe > Found: Q:\progs.win\cygwin\bin\gdb.exe > Found: Q:\progs.win\cygwin\bin\grep.exe > Found: c:\PROGRA~1\Borland\CBUILD~1\Bin\grep.exe > Warning: Q:\progs.win\cygwin\bin\grep.exe hides > c:\PROGRA~1\Borland\CBUILD~1\Bin\grep.exe > Found: Q:\progs.win\cygwin\bin\ld.exe > Found: Q:\progs.win\cygwin\bin\ls.exe > Found: c:\bin\ls.exe > Warning: Q:\progs.win\cygwin\bin\ls.exe hides c:\bin\ls.exe > Found: \bin\ls.exe > Warning: Q:\progs.win\cygwin\bin\ls.exe hides \bin\ls.exe > Found: Q:\progs.win\cygwin\bin\make.exe > Found: \bin\make.exe > Warning: Q:\progs.win\cygwin\bin\make.exe hides \bin\make.exe > Found: Q:\progs.win\cygwin\bin\mv.exe > Found: Q:\progs.win\cygwin\bin\rm.exe > Found: \bin\rm.exe > Warning: Q:\progs.win\cygwin\bin\rm.exe hides \bin\rm.exe > Found: Q:\progs.win\cygwin\bin\sed.exe > Found: c:\bin\sed.exe > Warning: Q:\progs.win\cygwin\bin\sed.exe hides c:\bin\sed.exe > Found: \bin\sed.exe > Warning: Q:\progs.win\cygwin\bin\sed.exe hides \bin\sed.exe > Found: Q:\progs.win\cygwin\bin\sh.exe > Found: c:\bin\sh.exe > Warning: Q:\progs.win\cygwin\bin\sh.exe hides c:\bin\sh.exe > Found: \bin\sh.exe > Warning: Q:\progs.win\cygwin\bin\sh.exe hides \bin\sh.exe > Found: Q:\progs.win\cygwin\bin\tar.exe > Found: c:\Programme\VisiQuest\bin\win32vs7\tar.exe > Warning: Q:\progs.win\cygwin\bin\tar.exe hides > c:\Programme\VisiQuest\bin\win32vs7\tar.exe > - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDSl0K84KuGfSFAYARAlJOAKCv71vweQIoqi8dox0+Tdh39aeJvQCglqjl 3BwhMx8u1DLjaAGlrgWEZJg= =Rvzg -----END PGP SIGNATURE----- -- 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/