Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 23 Jun 2005 11:22:36 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.5.17: problem building GNU screen Message-ID: <20050623152236.GA2124@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050618154511.GB23351@trixie.casa.cgf.cx> <42BAACE7.1090306@byu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/