X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 26 Feb 2009 19:50:10 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [1.7] "broken" pipe implementation? Message-ID: <20090227005010.GA11675@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090219142734 DOT GA22666 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090219142734.GA22666@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Thu, Feb 19, 2009 at 09:27:34AM -0500, Christopher Faylor wrote: >On Thu, Feb 19, 2009 at 09:16:50AM -0500, Andrew Schulman wrote: >>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. It qualifies as a "What in the world was I thinking?" problem. Thanks for the test case. 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/