On Tue, Jul 1, 2014 at 2:40 AM, Warren Young wrote:
> 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
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 w
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
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 fi
4 matches
Mail list logo