This is the mail archive of the
mailing list for the Cygwin project.
Re: Failure with fork()
- From: Peter Rosin <peda at lysator dot liu dot se>
- To: cygwin at cygwin dot com
- Cc: irwin at beluga dot phys dot uvic dot ca
- Date: Thu, 27 Jun 2013 22:48:40 +0200
- Subject: Re: Failure with fork()
- References: <alpine dot DEB dot 2 dot 02 dot 1306271112580 dot 27492 at enira dot zlyna dot ubzr> <alpine dot DEB dot 2 dot 02 dot 1306271148230 dot 27492 at enira dot zlyna dot ubzr> <51CC8EE9 dot 1080401 at gmail dot com> <alpine dot DEB dot 2 dot 02 dot 1306271225460 dot 27492 at enira dot zlyna dot ubzr>
On 2013-06-27 22: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
I think the real reason is that setup has downloaded and installed
cygwin1.dll, and is using it when running the post-install scripts.
There is no statically linked cygwin library in setup.exe.
> 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
If the procedure in  is too complicated, you will have to wait for
a new cygwin package to be released.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple