From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32710 invoked by alias); 27 Jun 2013 20:47:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 32650 invoked by uid 89); 27 Jun 2013 20:47:48 -0000 X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_00,BOTNET,EXECUTABLE_URI,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE autolearn=no version=3.3.1 Received: from vms173003pub.verizon.net (HELO vms173003pub.verizon.net) (206.46.173.3) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 27 Jun 2013 20:47:46 +0000 Received: from [192.168.1.231] ([unknown] [108.20.163.251]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MP200GCBKFCB160@vms173003.mailsrvcs.net> for cygwin@cygwin.com; Thu, 27 Jun 2013 15:47:42 -0500 (CDT) Message-id: <51CCA4E8.1040601@cygwin.com> Date: Thu, 27 Jun 2013 20:48:00 -0000 From: "Larry Hall (Cygwin)" Reply-to: cygwin@cygwin.com 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@cygwin.com Subject: Re: Failure with fork() References: <51CC8EE9.1080401@gmail.com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-SW-Source: 2013-06/txt/msg00704.txt.bz2 On 6/27/2013 4:33 PM, 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. No not really. 'setup.exe' is a pure Windows executable. It doesn't rely on cygwin1.dll at all. However, as part of the installation process for individual packages, there are (possible) preremove and postinstall scripts. These are shell scripts that invoke Cygwin utilities. These utilities, therefore, use cygwin1.dll. This is where you were seeing the problem. > I have looked at the table of contents of the latest > cygwin-inst-20130619.tar.bz2 since that appears to be the most > complete recent snapshot version. Although it does contain a number > of *.exe files and other core components of cygwin as advertised it is > missing many components of Cygwin that I need. Also, it is missing > the key setup.exe core component which precludes any chance of > installing the rest of what I need based on this snapshot version of > Cygwin. 'setup.exe' is built from separate sources. See for details. But I don't think this is really what you want. > So the question still remains how do I gain access to a version of > setup.exe with the fork fix that will allow me to not only initialize > my Cygwin distribution for Wine without the fork abort, but also > subsequently update it to install all components of Cygwin that I > need? Since you want to just run 'setup.exe', you need a new cygwin package (i.e. cygwin-1.7.2*-*) before you'll be able to do what you want without any extra effort on your part. So unless you're willing to build your own version of this package and put it in your download directory in the appropriate spot (after you've downloaded the packages you want), you want to just wait for the next announcement for the cygwin package. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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