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=F7A27 sxaNQgr0EqY2N/MbLnMQigQ9V0e81VrFcfkH89RWKzCHpks5W1XgfG8Q3N6rrC87 /RE4vCsjHhJtU/JzuFIjfGCCXW7SZk4KkgaToJnLQiDa+NK2ZI5Vus1zo9jX8LGt LKjVyXZ890xtLcRzjqbzs5BXoqXVF366H2nraU= 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=LJ+vwDEP/KG cOJbCwumRBf5c9OI=; b=SUW4552nYpLOOobKDjLa6hfuAIoHdtwRbpfXRscIDiM DPSn9uGRtjDUOw9ol+vHlyYBrFXbEq3ADBbMZlGruQFCSEOoLx5BMv9sycHQeJeE +XeYyDvxsKz3txDKMdzXg9DVvGyjZpgE10rTseA6AG8gM/FS3BpIYkoIz5XIMetQ = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Unless, Hx-languages-length:1437, suspend, WAVE X-HELO: mail-in-05.arcor-online.net X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-09.arcor-online.net 3sn3Mc1zQNz9hrT From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: Setup problem: no /home/ References: Date: Sun, 02 Oct 2016 13:47:52 +0200 In-Reply-To: (Matthijs Nescio's message of "Sat, 1 Oct 2016 18:48:51 +0000") Message-ID: <87vaxb3rbr.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Matthijs Nescio writes: > I am using Windows 7. During the setup, the install has hung after it > was finished, running some postinstall script for quite some time. It seems you aborted setup or your log files are truncated. Unless you let it finish the postinstall phase, you can't expect Cygwin to work correctly or at all. That said, after over an hour it hasn't got very far into the autorebase based on your logs, so I suspect that the same effect that makes the invocation of ls take so long is at play, most likely some sort of BLODA. It seems the install itself went OK, so if you can temporarily suspend your virus scanner or except the Cygwin install directory from any real-time checking, that would probably help. > One of the links suggests to run cygcheck -csv; the results are copied > below. It sais my PC has multiple cygwin1.dll files. > > -bash-4.3$ find /cygdrive/c/cygwin64 -name "cygwin1.dll" > /cygdrive/c/cygwin64/bin/cygwin1.dll > /cygdrive/c/cygwin64/usr/i686-pc-cygwin/sys-root/usr/bin/cygwin1.dll > ./cygwin1.dll > /cygdrive/c/cygwin64/bin/cygwin1.dll > /cygdrive/c/cygwin64/usr/i686-pc-cygwin/sys-root/usr/bin/cygwin1.dll > -bash-4.3$ Don't put "." in your PATH. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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