X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=QK+eVg7qLivx2MuqzFDyngNTqxe7ATb7znI6+fbETAk
	7eRgr9h/tPwNeC17kYI3w4iEcmAMtCJBR4igZsqgKpiplfKTH0uTjqRjBx4SDYDr
	pMfdIXMKenTg+N5pNqIyTIvkxuFLNZjVy07gpiHATJ+qQoRCThxBb2bXWgYAUpzY
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=s3iY88fmYnzjTMLcl9G2DSNA3Hs=; b=ye5ITuCdW7IspZFGl
	Wdt6aBv74h/ttcxrUigjnW7/qsE5UUc4v5RMneOTr9pBU76H1eezGx64R3gflppX
	M4lrA+pEfuLjDZErsztmaE64QF+/bPKDdUIcwC041bDnpDojGZG8STttD6r0MHq2
	4WQGzY2yl4HD10Y5YZYLcHrAB8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,T_RP_MATCHES_RCVD,UNSUBSCRIBE_BODY autolearn=no version=3.3.2
X-HELO: etr-usa.com
Message-ID: <53B20373.4010100@etr-usa.com>
Date: Mon, 30 Jun 2014 18:40:19 -0600
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: can't share fifo between 32-bit and 64-bit Cygwins
References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8967 AT USA7109MB022 DOT na DOT xerox DOT net> <53B1C3B8 DOT 9080401 AT gmail DOT com> <20140630231824 DOT GA7883 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20140630231824.GA7883@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 6/30/2014 17:18, Christopher Faylor wrote:
> On Mon, Jun 30, 2014 at 10:08:24PM +0200, Marco Atzeri wrote:
>> On 30/06/2014 20:04, Nellis, Kenneth wrote:
>>>
>>> If I create a named pipe (mkfifo), as long as I write to and read from using
>>> either 32-bit Cygwin or 64-bit Cygwin, all works fine, but if I write with either
>>> one and read with the other, both processes hang.
>>
>> why do you expect such things to work ?
>> You have two separate simulation layers independent from each other.
>> Nothing is in place to pass the data from the 32 bit layer to the 64 layer.
>
> Right.  Fifos, signals, ptys - all of them are distinct entities that won't
> work between 32 bit and 64 bit or even between different Cygwin installations
> on the same system.

In principle, one could build a 32-bit cygwin1.dll that would depend on 
the existence of a 64-bit cygwin1.dll, doing nothing other than acting 
as a thunking layer.  Every 32-bit Cygwin app that makes a call on that 
DLL would actually be talking to the 64-bit DLL, which would do all the 
work.

Microsoft has done such trickery several times to my knowledge, but MS 
has lots of financial incentive to do go to the effort it takes to build 
such things.  It's not trivial.

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