public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Failure with fork()
Date: Thu, 27 Jun 2013 19:01:00 -0000	[thread overview]
Message-ID: <51CC8BB8.40607@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306271112580.27492@enira.zlyna.ubzr>

Il 6/27/2013 8:35 PM, Alan W. Irwin ha scritto:
> I have been following this thread with great interest via the archive,
> but now I have newly subscribed to this list to ask additional
> questions.
>
> Corinna said "Should be fixed in CVS.  Thanks (to Arjen) for the report."
>
> My thanks to Arjen for getting this thread started, and
> my thanks to Corinna for so swiftly finding the fix.
>
> I would now like to test this fix from a broader perspective of
> attempting to run the fixed setup.exe version on Wine.
>
> My background is I have had considerable success with using the
> combination of MinGW, MSYS, and Wine as a build and test platform for
> free software.  I would like to similarly attempt to use the
> combination of Cygwin and Wine as a build and test platform for free
> software but I was stopped from doing that because the last stage of
> running Cygwin setup.exe on Wine ran into this fork issue.
>
> 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?

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

>
> Or do I have to build the CVS version of Cygwin from scratch on (the
> Wine version of) Windows using MinGW and MSYS, and if so is there a
> website with directions for how to do that?
>
> Sorry for the Cygwin newbie questions, but I am quite experienced with
> the Unix command line and building software both on Linux and on the
> bash.exe command line accessible with MinGW/MSYS/Wine so I hope I will
> only need hints to get started with (a) building the CVS version
> of Cygwin with the fork fix, and (b) building and testing software for
> the Cygwin on Wine platform.
>
> Alan
> __________________________
> Alan W. Irwin
>

Regards
Marco


--
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

  reply	other threads:[~2013-06-27 19:00 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 [this message]
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
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=51CC8BB8.40607@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).