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
X-Authentication-Warning:	ares.its.yale.edu: lsb32 owned process doing -bs
Date:	Thu, 14 Apr 2005 08:37:24 -0400 (EDT)
From:	Lev S Bishop <lev DOT bishop AT yale DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bash Process Substitution
Message-ID:	<Pine.LNX.4.44.0504140824250.19852-100000@ares.its.yale.edu>
MIME-Version:	1.0
X-YaleITSMailFilter:	Version 1.2b (attachment(s) not renamed)

Brian Dessent wrote:
> If I'm not mistaken /proc/<pid>/fd capabilty was added 2005-02-01.  The
> current bash package (2.05b-16) was released 2003-10-23.  (the test
> version -17 was released 2004-11-22.)  So it was quite impossible for
> the person who built bash to have that feature.

Thanks for this piece of info, Brian. It saved me from barking up
completely the wrong tree. Things are becoming clearer. I guess what
happened is that the binary build of bash used fifos, which have only ever
been partially implemented in cygwin, and although at one point in the
past they worked well enough for process substitution's needs, in the
meantime the implementation has changed sufficiently to break that. The
version of bash that I built uses /proc/self/fd, which is a brand spanking
new feature that also doesn't quite work in terms of process substitution
on output. (Is this all plausible?)

Its either that, or process substituion never worked at all on cygwin, my 
memory is completely flawed, and these nifty scripts I have here were 
copied from a non-cygwin box. (This is certainly plausible.)

Lev


--
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 -