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:cc:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=d+NiQuun3TDBYuts2xoIOI83kav8Rp3dWrEvJ1i1bia
	BFfav5G8yanYEoTlUJE3h81Mvgi4XRt0gYmLvYVBWhImX++zNx4Vf1rPVcmohLOW
	lILPnSfxoOfrVKoeF1fVyxQWNHfWFjBF9+23e7refI+WDKnDc5ebqYZ/BhxEwB1M
	=
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:cc:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=6tn7T9X0KkDPGDrRqUaMn1LIh5Q=; b=uhH+s8klyUNuHoh60
	PvvOwSUgTiyE7i06HDO0W9ZplM1BwQMJPZOtJiKjm13Z9zIGLPH2XRWJ9Hed53e9
	7VfdDhOLDpvG8FXzcgL2eXDCXhrxQwbMeKlGCDt1rnLmImkFj+KLBrGZkTIKex+e
	ECQh9rdyEd7mKH9FfqxlnqAxLY=
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
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
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)
From:	<gmt AT malth DOT us>
To:	<cygwin AT cygwin DOT com>
Cc:	"'Alan W. Irwin'" <irwin AT beluga DOT phys DOT uvic DOT ca>
References:	<alpine DOT DEB DOT 2 DOT 02 DOT 1306271112580 DOT 27492 AT enira DOT zlyna DOT ubzr> <51CC8BB8 DOT 40607 AT gmail DOT com> <alpine DOT DEB DOT 2 DOT 02 DOT 1306271205210 DOT 27492 AT enira DOT zlyna DOT ubzr>
In-Reply-To:	<alpine.DEB.2.02.1306271205210.27492@enira.zlyna.ubzr>
Subject:	RE: Failure with fork()
Date:	Thu, 27 Jun 2013 13:19:46 -0700
Message-ID:	<002b01ce7373$abea85f0$03bf91d0$@malth.us>
MIME-Version:	1.0
X-Gm-Message-State:	ALoCoQnXZm3D+YURuqyJTNnEWbpvYl50f/jqG5YrmZTQMv2Y4s5fH5rW7GdmCdgv/pxatcve3hCP
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id r5RKK5tt027155

on Thu, 27 Jun 2013, at 12:22, Alan W. Irwin thusly quipped:
> On 2013-06-27 21:00+0200 marco atzeri wrote:
> 
>> Il 6/27/2013 8:35 PM, Alan W. Irwin ha scritto:
>>> Are there daily snapshot builds of the CVS version I could access?
>> 
>> daily not, but on reasonable schedule
>> (aka when Corinna or Christopher release one)
>> 
>> http://cygwin.com/snapshots/
>> 
>> just wait for the next cygwin1-20130xxx.dll.bz2
>> and replace the installed cygwin1.dll with the new one
> 
> I haven't even gotten as far as an initial install because
> of this fork bug.
> 
> 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:
> 
> 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://cygwin.com/cvs.html, and, from there, follow a fairly typical cross-compiling configure && make && make install DESTDIR=foo && 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 setup.exe prompts you to put those packages back in, uncheck the box (by default, checked) specifying to add them.

Assuming you get that far, successfully, you'd then expect to see some results -- either finding the next bug, discovering the bug still exists, somehow, 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 default generates "setup.exe"-compatible package-trees that, if I'm not mistaken, by following easily-google-able advice, can be overlaid into your setup.exe's package-set so that you could follow a standard setup.exe process without having to uncheck those core packages.

No idea what results you'll get -- very likely an anticlimax where you simply find the next bug -- but one of the above would probably allow you to proceed; worst-case you'd at least have a build environment, for future testing/hacking, that you could recycle. 

-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

- Raw text -