X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=CGaUK
	viQmGlwRuNDAf7KitlOZR12iPNnADgXBFnBo+FvYnyLY/hhEkGFIQR/jkCIs8eYf
	XL3JVJeN4pWtvEscYr30FNOBasOIwZKaN0BX1o2Q1D4FiRn79Q1qr7SyzjjWoKcX
	QvfE0kC59BK2HIZ8EaZPeSGhqV9XH4TxgAYnXY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=yn5j9vW8Xn9
	N1yWqou0yjmquj68=; b=nlxgZcwgNtbiMHTDvo+O0FNga53WC2xz9bkHWuYuO0J
	Kwyjv75Hv1YlUocVKX+tvAXzri+Ctt0V/P0L+BAMHciOPAdOriojCyPdWlvWY+iv
	7pjOUlfDv+XYBiNxFKsV3cUMHaGYU9W9U1aOQehQlhrcdZR1vOXP3zZeAiyOT9h0
	=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=_prepdash, dashexe, UD:_prep.dash, Ending
X-HELO:	mail-in-10.arcor-online.net
X-DKIM:	Sendmail DKIM Filter v2.8.2 mail-in-10.arcor-online.net 3pmZb76xkTz8SBR
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: New cygwin install hanging on postinstall
References:	<B8D164BED956C5439875951895CB4B2250BAE63C AT CAFRFD1MSGUSRJH DOT ITServices DOT sbc DOT com> <CANnLRdi5sqTnOmen7oufLFJEi+wZX4BuGpfD58Wf8i7=NfEt9Q AT mail DOT gmail DOT com> <B8D164BED956C5439875951895CB4B2250BB0354 AT CAFRFD1MSGUSRJH DOT ITServices DOT sbc DOT com>
Date:	Thu, 21 Jan 2016 21:10:27 +0100
In-Reply-To:	<B8D164BED956C5439875951895CB4B2250BB0354@CAFRFD1MSGUSRJH.ITServices.sbc.com> (DAVID KARR's message of "Thu, 21 Jan 2016 17:40:31 +0000")
Message-ID:	<877fj28zik.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version:	1.0

KARR, DAVID writes:
> While it's sitting here, I dumped out "/var/log/setup.log.full".  Here is the end of the file:
> ----------------
> The following DLLs couldn't be rebased because they were in use:
>   /usr/bin/cygssp-0.dll
>   /usr/bin/cygperl5_22.dll
>   /usr/bin/cyggcc_s-1.dll
>   /usr/bin/cygcrypt-0.dll
>   /usr/lib/perl5/vendor_perl/5.22/i686-cygwin-threads-64int/auto/List/Util/Util.
> dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/IO/IO.dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/File/Glob/Glob.dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Fcntl/Fcntl.dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Encode/Encode.dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Digest/MD5/MD5.dll
>   /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Cwd/Cwd.dll
> 2016/01/21 09:15:40 running: C:\cygwin\bin\dash.exe "/etc/postinstall/0p_texlive
> _prep.dash"
> 2016/01/21 09:19:20 note: Nothing needed to be installed
> 2016/01/21 09:19:20 Ending cygwin install
> -----------

So this isn't a fresh install and in fact there is not only some Cygwin
process running but a full blown Perl that has loaded a number of
modules.  How'd you manage to do that before Cygwin was ready
installing?  Are you perhaps reporting from a follow-on invocation of
setup.exe after the first install already failed?

For your current case, you need to get rid of _all_ running Cygwin
processes.  Best idea is to open a shell and issue

  /usr/bin/rebase-trigger fullrebase
  /usr/bin/pkill .

(you need to have procps installed for this command to be available).
Then run setup again to have it re-do the rebase and run all postinstall
scripts that failed before.  But I'm still interested how that initial
failure could have occured, so if you could maybe look in
/var/log/setup.log if something indicates what happened there that would
be good.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -