From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1792 invoked by alias); 27 Jun 2013 20:19:56 -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 1778 invoked by uid 89); 27 Jun 2013 20:19:55 -0000 X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,EXECUTABLE_URI,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS,TW_YG autolearn=no version=3.3.1 Received: from mail-pb0-f41.google.com (HELO mail-pb0-f41.google.com) (209.85.160.41) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 27 Jun 2013 20:19:54 +0000 Received: by mail-pb0-f41.google.com with SMTP id rp16so1384251pbb.0 for ; Thu, 27 Jun 2013 13:19:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:sender:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language:x-gm-message-state; bh=KAao8mxQzjsZ28IrBDwLXjKibmWblbIWyyyVCofGVV0=; b=S0wdY5xdtmqmI0waGb8o9+BZ0zcwGehNIop8AQGi04LJRBik5+OyzI/58MFpqYcu6V UrUtrpguHJOlqg6jYUY7IBkX9v1W0GOzqo0l7vzsAgrbEVcpCV7WTQ8crmc1hAOlUT5d ghbaxOKZ6waBBlkHX+Hx80BOcEZo/aB2T9OHRYLS1BHuGbJxvMHk95V6nmC+bdA1c2sE a0A+UZl3k8TLVntl6G1AcnB1IwuMbpQv4BfClRaIazIHvgUkEbOi0eAz2XRjrxIdEdr+ 5scxrfgopAJSzWJ/SxlSB/F25nq+4oclFpLxIaG/1hqDIz9U5PwP93ofqJnNAUPkO85B hYlA== X-Received: by 10.66.232.101 with SMTP id tn5mr7913504pac.132.1372364393088; Thu, 27 Jun 2013 13:19:53 -0700 (PDT) Received: from weaksauce (malth.us. [75.147.143.249]) by mx.google.com with ESMTPSA id ai6sm5221002pad.15.2013.06.27.13.19.51 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 27 Jun 2013 13:19:52 -0700 (PDT) From: To: Cc: "'Alan W. Irwin'" References: <51CC8BB8.40607@gmail.com> In-Reply-To: Subject: RE: Failure with fork() Date: Thu, 27 Jun 2013 20:33:00 -0000 Message-ID: <002b01ce7373$abea85f0$03bf91d0$@malth.us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnXZm3D+YURuqyJTNnEWbpvYl50f/jqG5YrmZTQMv2Y4s5fH5rW7GdmCdgv/pxatcve3hCP X-SW-Source: 2013-06/txt/msg00700.txt.bz2 on Thu, 27 Jun 2013, at 12:22, Alan W. Irwin thusly quipped: > On 2013-06-27 21:00+0200 marco atzeri wrote: >=20 >> Il 6/27/2013 8:35 PM, Alan W. Irwin ha scritto: >>> Are there daily snapshot builds of the CVS version I could access? >>=20 >> daily not, but on reasonable schedule >> (aka when Corinna or Christopher release one) >>=20 >> http://cygwin.com/snapshots/ >>=20 >> just wait for the next cygwin1-20130xxx.dll.bz2 >> and replace the installed cygwin1.dll with the new one >=20 > I haven't even gotten as far as an initial install because > of this fork bug. >=20 > From the Linux command line here is what I did some time ago (for a > wine-git version very close to wine-1.6.0-rc1 and for (presumably) the > latest stable release of setup.exe downloaded from > http://cygwin.com/setup.exe) when I first ran into the fork bug: >=20 > wineconsole setup.exe I haven't tried this myself (yet), but if you "can't wait", and have access= to a mingw64 cross-compiler, you can likely get cygwin cvs here: http://cy= gwin.com/cvs.html, and, from there, follow a fairly typical cross-compiling= configure && make && make install DESTDIR=3Dfoo && tar type of process to = create your own "ghetto" snapshot, that you could drop into place on top of= your your half-completed nascent cyg-wine install. From there, you could = run setup.exe, uncheck the "cygwin" and "newlib" packages, and then, when s= etup.exe prompts you to put those packages back in, uncheck the box (by def= ault, checked) specifying to add them. Assuming you get that far, successfully, you'd then expect to see some resu= lts -- either finding the next bug, discovering the bug still exists, someh= ow, or that everything is magically fixed... what-have-you. Alternatively, you could try to create a cross-cygport. Not sure how easy/= hard that is, but I'd guess it's fairly straightforward. Cygport by defaul= t generates "setup.exe"-compatible package-trees that, if I'm not mistaken,= by following easily-google-able advice, can be overlaid into your setup.ex= e's package-set so that you could follow a standard setup.exe process witho= ut having to uncheck those core packages. No idea what results you'll get -- very likely an anticlimax where you simp= ly find the next bug -- but one of the above would probably allow you to pr= oceed; worst-case you'd at least have a build environment, for future testi= ng/hacking, that you could recycle.=20 -gmt -- 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