From: Vin Shelton <acs@alumni.princeton.edu>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Test D03 hang under cygwin 1.7
Date: Fri, 6 Feb 2009 16:07:30 -0500 [thread overview]
Message-ID: <20a807210902061307l1a95eeacl66e9d02a40e07b4c@mail.gmail.com> (raw)
In-Reply-To: <20090206163325.0a5db68a@news01>
On Fri, Feb 6, 2009 at 11:33 AM, Peter Stephenson <pws@csr.com> wrote:
> On Fri, 6 Feb 2009 09:56:26 +0000
> Peter Stephenson <pws@csr.com> wrote:
>> On Thu, 5 Feb 2009 23:07:24 -0500
>> Vin Shelton <acs@alumni.princeton.edu> wrote:
>> > Under the soon-to-be-released Cygwin 1.7, I downloaded the latest CVS
>> > sources and ran a build from scratch. I'm getting a test hang in D03:
>>
>> This is process substitution again. This is problematic under Cygwin:
>> sometimes one of the two forms works, sometimes another, even though both
>> are notionally present and zsh is simply using documented behaviour that
>> works on other systems. (The real problem, of course, is that process
>> handling is intrinsically horrific in Cygwin.)
>>
>> I don't think we can do much more than skip the test and put a warning
>> about related features in the manual. We might be able to add an option to
>> pick the support we use (named pipes or device files) but that's probably
>> only of use to the sort of people who could in any case hack the
>> configuration by hand.
>
> ... in fact, could you try #define'ing PATH_DEV_FD in config.h (it's turned
> off by a special test in configure) and see if that works with the new
> version of Cygwin? We can always reverse the configured default when that
> comes out.
Yes, that enables D03 to pass. Thank you!
- Vin
next prev parent reply other threads:[~2009-02-06 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 4:07 Vin Shelton
2009-02-06 9:56 ` Peter Stephenson
2009-02-06 16:33 ` Peter Stephenson
2009-02-06 21:07 ` Vin Shelton [this message]
2009-02-07 6:32 ` Peter A. Castro
2009-02-13 11:50 ` Vin Shelton
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=20a807210902061307l1a95eeacl66e9d02a40e07b4c@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).