Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Norbert Harendt <n DOT harendt AT ib-eckerl DOT de>
Subject:  Re: cygwins setup hangs in installation
Date: Mon, 10 Oct 2005 13:27:17 +0000 (UTC)
Lines: 31
Message-ID:  <loom.20051010T152159-620@post.gmane.org>
References:  <loom DOT 20051010T101606-565 AT post DOT gmane DOT org> <434A5D0A DOT 9070608 AT byu DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Eric Blake <ebb9 <at> byu.net> writes:

> 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.  

But to my opinion in my special case some routine invoked during 
postinstall (or the invocation of child child processes) REALLY does 
nothing, because i waited a very, very .. very long time for the 
postinstallation to complete, which doesn't. So there must be something 
going wrong.

> 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.

I'll try to remove the conflicts and see, if this is the solution.
> 
> > 
> > Found: Q:\progs.win\cygwin\bin\awk.exe
> > Found: Q:\progs.win\cygwin\bin\bash.exe
> > Found: c:\bin\bash.exe ...



--
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/