This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin FIFO support
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com, "Justin T. Gibbs" <gibbs at scsiguy dot com>
- Date: Sun, 19 Mar 2006 19:19:04 -0500
- Subject: Re: Cygwin FIFO support
- References: <9FE5BCEE20D455B21F70A234@[192.168.0.85]>
- Reply-to: cygwin at cygwin dot com
On Sun, Mar 19, 2006 at 03:22:15PM -0700, Justin T. Gibbs wrote:
>I have an application (build tool) that seems to break cygwin's current
>FIFO support. I've Googled a bit and it sounds like this is a known
>issue. [In my case, the fifo master reads and writes to the fifo and
>so do its child processes. Unfortunately, even though the fifo master
>is also a reader of the fifo, its second attempt to write the fifo blocks.
>Each write is only 1 byte and the file descriptor is set to nonblocking
>Since I have an immediate need for this to work, I'm happy to fix this
>myself. Do you have any notes, documentation, or hints that might help
>me to understand the current FIFO implementation and/or how I might fix
>it? I've pulled down the latest cygwin sources, built the DLL and
>started to trace my way through the sources, but I'd appreciate any
Please check out the project web page for links to available information
and ports: http://cygwin.com/ .
If you don't see what you need there, then the cygwin mailing list is
the best place to make observations or get questions answered.
Information on the mailing list is available at the project web page.
For your convenience, I've reset the Reply-To: address to point to the
cygwin mailing list. I've also Cc'ed this reply there.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html