Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 23 Jun 2005 11:22:36 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.17: problem building GNU screen
Message-ID:	<20050623152236.GA2124@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<uoea630iy.wl%atara-y AT mx DOT scn DOT tv> <d90v40$rsl$1 AT sea DOT gmane DOT org> <20050618154511 DOT GB23351 AT trixie DOT casa DOT cgf DOT cx> <42BAACE7 DOT 1090306 AT byu DOT net>
Mime-Version:	1.0
In-Reply-To:	<42BAACE7.1090306@byu.net>
User-Agent:	Mutt/1.5.8i

On Thu, Jun 23, 2005 at 06:36:56AM -0600, Eric Blake wrote:
>According to Christopher Faylor on 6/18/2005 9:45 AM:
>> IMO, the posted check for fifos is flawed in that it assumes that
>> writing to a fifo will not block if there is no reader on the fifo.
>> That's not true for cygwin.
>
>The posted check for fifos used the O_NONBLOCK flag when opening the fifo
>for writing,

Oops.  I missed that.  Yes, that's a cygwin bug.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -