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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=lGWvWPTq9V6HU3H8MYL/bdRPT+iFrVVtDS0+SjnIKD8zlC/mxqhZ3 zM4Pe+aXRh8J6AZg5vA8f2oZex+JMr0+SSXA6qjCJySTM65yPUKT0ApnUgWJ1kWX ds2xC1yFUmrWxIsJs/Fha/jPBZbHCKxPhJF497B4BosM/28wEoXBc4= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=FHDQxUJuIgV1hFdF1ktxoIgbwsw=; b=hvQnbZvy1oMaXP3ee9KVdQ+5BRPf i8C4hJg0n59duK3ELIvTdb4vM5yo2BFZpNF/K+omCzni8ah8iXFvI+NPy2QOIg0R PmMKIzWq6g7vl6y8bk4ciRhuw8kIMVx6XAfcAdLcvAZp/awlQ8BGL3sjnZjL9lBC ez1kReQ1dd7GLBU= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 X-HELO: mho-01-ewr.mailhop.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19CU63VILph2OzlqN6RGJIZ Date: Mon, 30 Jun 2014 19:18:24 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: can't share fifo between 32-bit and 64-bit Cygwins Message-ID: <20140630231824.GA7883@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8967 AT USA7109MB022 DOT na DOT xerox DOT net> <53B1C3B8 DOT 9080401 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53B1C3B8.9080401@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) On Mon, Jun 30, 2014 at 10:08:24PM +0200, Marco Atzeri wrote: >On 30/06/2014 20:04, Nellis, Kenneth wrote: >> Just thought I'd share an observation I found interesting. >> Not a problem for me, so not asking for any particular response. >> >> 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. >> >> It doesn't seem to matter whether the fifo was created under 32-bit or >> 64-bit, the problem (if I may be so bold as to call it that) seems only with >> mixing 32-/64-bit versions doing I/O to/from it. >> >> FWIW, using 32-bit version 1.7.29-2 and 64-bit version 1.7.30-1. > >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. cgf -- 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