X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: [1.7] "broken" pipe implementation? Date: Fri, 27 Feb 2009 11:10:28 -0500 Lines: 21 Message-ID: References: <20090219142734 DOT GA22666 AT ednor DOT casa DOT cgf DOT cx> <20090227005010 DOT GA11675 AT ednor DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > >>I'm compiling screen for 1.7. The configure script has a test for a "usable" > >>pipe implementation, which passes, and another one for a "working" pipe > >>implementation, which fails. The test for a working pipe implementation is zero > >>exit code from the following program (simplified for clarity): > > > >I'll look into this sometime today. > > ...or maybe a little later. > > This should be fixed in the latest snapshot. Confirmed, thanks. With the 2009-02-26 snapshot, the working pipe test succeeds, and screen now runs just fine AFAICT with fifos, for the first time ever. Not sure yet whether that will fix any of the occasional odd bugs, but we'll find out and it's good to have it available to try. > It qualifies as a "What in > the world was I thinking?" problem. No idea what that is. A. -- 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/