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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=v7YQHSO+GqEFWSwwgiZqfbSEYn5qJB3RehmPj2sHiLw jfbqTdg+qSHMieQ0+BzCdXqw6I/b20ReuhtzJKAgz2Ta85hzSISJ/2x9hSkhwCWG R4HScTBPFa5oQTQ8YqsabjxiGnetDbJLfRsy98po2bhYVpKoJ8XpkQAydO/+Yhy4 = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=CUs//KNLBV6M7uB+d1WHq5FgaHI=; b=oEdoythR900B1hpH7 sb9+pkvqE/2b9xwzVlCwq7nAYqFao/IIclf5NrRUD6+JzwA67Fg7OWF6eVhrtbGy sBvs0g98TpV/rgoj9bXyBC4CWhUWaLh6gUOqcr4g7jhLBgt65rGbfXrUAGfND/8z 6fxE+5+WblQvBqBpzPjOMG23Ek= 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 X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,EXECUTABLE_URI,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=no version=3.3.1 X-Received: by 10.66.251.202 with SMTP id zm10mr8059961pac.53.1372366584101; Thu, 27 Jun 2013 13:56:24 -0700 (PDT) Message-ID: <51CCA6FB.5060804@users.sourceforge.net> Date: Thu, 27 Jun 2013 15:56:27 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Failure with fork() References: <51CC8EE9 DOT 1080401 AT gmail DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2013-06-27 15:33, Alan W. Irwin wrote: > I think you keep assuming I have some version of Cygwin already > installed when that is not the case. It is the last stage of the > initial attempt at installation using setup.exe that fails on Wine due > to the fork bug. Furthermore, when I download setup.exe from > http://cygwin.com/setup.exe it contains the fork bug. That version is > self-contained, i.e., only setup.exe needs to be downloaded, not > cygwin1.dll in addition. I presume that is because setup.exe uses a > static version of the cygwin library as a matter of convenience rather > than depending on an external cygwin1.dll that could be separately > downloaded. There is no such thing as static linkage of Cygwin. setup.exe is in fact a native Windows (MinGW) executable, due to the fact that it needs to be able to run before Cygwin is installed, or while upgrading cygwin1.dll. Therefore, if you are seeing fork() errors when running setup, they are actually coming from the postinstall scripts which are run after installing files. In that case, the best solution may be something along the lines of (untested): 1) Open the Wine equivalent of taskmgr.exe. 2) Run setup.exe again and install just the Base packages. 3) During postinstall, kill any bash.exe processes ASAP. 4) setup.exe should list some postinstall errors before completion, which can be ignored for now. 5) After setup.exe is finished, replace C:\cygwin\bin\cygwin1.dll with the latest snapshot DLL. 6) Run setup.exe again with the same options; the postinstall scripts should (in theory) run properly this time. 7) Launch Cygwin Terminal once to set up your environment. 8) Run setup.exe one more time to install additional packages. HTH, Yaakov -- 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