From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Failure with fork()
Date: Thu, 27 Jun 2013 19:15:00 -0000 [thread overview]
Message-ID: <51CC8EE9.1080401@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306271148230.27492@enira.zlyna.ubzr>
Il 6/27/2013 9:01 PM, Alan W. Irwin ha scritto:
> On 2013-06-27 11:35-0700 Alan W. Irwin wrote:
>
>> The only Windows platform available to me is Wine. And I have
>> no Cygwin on Wine experience at this stage because this fork bug shut
>> me out. But now that it is fixed in CVS, how do I get access to
>> the fixed version of setup.exe?
>>
>> Are there daily snapshot builds of the CVS version I could access?
>
> Never mind. I have now found the snapshots page, and the latest one
> contains
>
> 013-06-18 Christopher Faylor <me.cygwin2013@cgf.cx>
>
> * dcrt0.cc (child_info_fork::alloc_stack): Don't subtract 4096 from
> stack pointer since getstack() already does that.
>
> Could someone confirm that is the fork fix of interest here?
Of course not. Corinna solved the problem today
and cygwin1-20130619.dll.bz2 was built last 19th June
so you need to wait the next one.
>
> I am somewhat confused by the remark
> at http://cygwin.com/faq-nochunks.html#faq.setup.snapshots
> that "You cannot use Cygwin Setup to install a snapshot."
>
> So what exactly is installed by a snapshot? Is it just the core part
> of Cygwin?
It is just the core cygwin1.dll
The easy way is copy the new one on the current one.
Of course all cygwin processes must be shutdown before..
> Is there enough included in cygwin-inst-YYYYMMDD.tar.bz2
> so I can run setup.exe from the installed version of that tarball to
> download and install or update additional Cygwin components that I
> might need?
>
> Alan
> __________________________
> Alan W. Irwin
>
>
--
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
next prev parent reply other threads:[~2013-06-27 19:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 18:58 Alan W. Irwin
2013-06-27 19:01 ` marco atzeri
2013-06-27 19:45 ` Alan W. Irwin
2013-06-27 20:17 ` Achim Gratz
2013-06-27 20:33 ` gmt
2013-06-27 19:13 ` Alan W. Irwin
2013-06-27 19:15 ` marco atzeri [this message]
2013-06-27 20:43 ` Alan W. Irwin
2013-06-27 20:47 ` Christopher Faylor
2013-06-27 20:48 ` Larry Hall (Cygwin)
2013-06-27 20:56 ` Thrall, Bryan
2013-06-28 1:28 ` Larry Hall (Cygwin)
2013-06-27 20:55 ` Peter Rosin
2013-06-27 21:52 ` Yaakov (Cygwin/X)
2013-06-27 21:58 ` Alan W. Irwin
2013-06-27 21:59 ` Yaakov (Cygwin/X)
2013-06-28 9:19 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2013-06-28 7:55 Alan W. Irwin
2013-06-28 7:59 ` marco atzeri
2013-06-28 8:52 ` Corinna Vinschen
2013-06-28 10:16 ` gmt
2013-06-28 10:20 ` Corinna Vinschen
2013-06-28 19:05 ` Alan W. Irwin
2013-06-28 8:42 ` Alan W. Irwin
2013-06-28 9:40 ` gmt
2013-06-27 10:49 Arjen Markus
2013-06-27 11:27 ` Ryan Johnson
2013-06-27 11:29 ` Corinna Vinschen
2013-06-27 12:19 ` Arjen Markus
2013-06-27 17:01 ` Corinna Vinschen
2013-06-27 17:03 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51CC8EE9.1080401@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).