This is the mail archive of the
mailing list for the Cygwin project.
Re: can't share fifo between 32-bit and 64-bit Cygwins
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 30 Jun 2014 19:18:24 -0400
- Subject: Re: can't share fifo between 32-bit and 64-bit Cygwins
- Authentication-results: sourceware.org; auth=none
- References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8967 at USA7109MB022 dot na dot xerox dot net> <53B1C3B8 dot 9080401 at gmail dot com>
- Reply-to: cygwin at cygwin dot com
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple