From: Ken Brown <kbrown@cornell.edu>
To: Michael McMahon <michael.x.mcmahon@oracle.com>,
sten.kristian.ivarsson@gmail.com, cygwin@cygwin.com
Subject: Re: Sv: Problems with native Unix domain sockets on Win 10/2019
Date: Tue, 16 Mar 2021 11:19:03 -0400 [thread overview]
Message-ID: <0cc7931c-6c07-755d-2d0c-1b62189fddd9@cornell.edu> (raw)
In-Reply-To: <c06b5537-b1f9-5ae7-fd85-8701c412239c@oracle.com>
On 3/16/2021 9:00 AM, Michael McMahon via Cygwin wrote:
> I think you can download pre-released builds from:
>
> https://cygwin.com/snapshots/
Right, but see below for cygwin-3.2.0-0.1.
> As mentioned already, the fix here is not actually support of AF_UNIX sockets
> natively. My understanding is that they are implemented over loopback TCP in
> cygwin, but the fix allows native AF_UNIX sockets to be handled (eg deleted) as
> regular files through regular cygwin commands.
>
> Michael.
>
>
> On 16/03/2021 11:06, Kristian Ivarsson via Cygwin wrote:
>> Hi all
>>
>> Does anyone know the status of these fixes ?
>>
>> I saw an announcement for cygwin-3.2.0-0.1 that seemed to contain some
>> AF_UNIX-related fixes but I fail to find out where that distribution exists
>> (if it is supposed to be publicly accessible?), but I tried out the
>> 2021-03-01 snapshot and perhaps they are similar ?
You can install cygwin-3.2.0-0.1 in the usual way, through Cygwin's setup
program. Since it's a test release, you'll have to explicitly select that
release; setup won't just offer it to you.
>> We bumped into some AF_UNIX-related issues when trying the 2021-03-01
>> -snapshot though. It might be some flaws in our code base but the same code
>> works in quite a few Linux-distros
>>
>> We're more than willing to help out with testing this and/or trying to
>> narrow down any possible cygwin issues, but first we'd be glad if someone
>> could give us some kind of status report of this (so no one is doing any
>> unnecessary work)
>>
>>
>> Best regards,
>> Kristian
>>
>> p.s.
>> I tried to build the topic/af_unix -branch according to the FAQ, but
>> there was some issues
I'm still in the middle of some things on that branch, and I haven't had much
time to work on it recently. I hope to get back to it very soon. In order to
build it, you need to add -D__WITH_AF_UNIX to CXXFLAGS. In order to test it,
you need
#undef AF_UNIX
#define AF_UNIX 31
after including <sys/socket.h>
Ken
next prev parent reply other threads:[~2021-03-16 15:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:25 Michael McMahon
2020-09-24 11:26 ` Ken Brown
2020-09-24 12:01 ` Michael McMahon
2020-09-24 17:11 ` Brian Inglis
2020-09-25 13:19 ` Ken Brown
2020-09-25 14:29 ` Michael McMahon
2020-09-25 14:37 ` Eliot Moss
2020-09-25 16:13 ` Michael McMahon
2020-09-25 16:32 ` Eliot Moss
2020-09-25 18:50 ` Ken Brown
2020-09-25 20:30 ` Ken Brown
2020-09-26 0:31 ` Duncan Roe
2020-09-26 1:22 ` Ken Brown
2020-09-26 7:30 ` Michael McMahon
2020-09-28 11:03 ` Michael McMahon
2021-01-30 16:00 ` Ken Brown
2021-01-31 23:30 ` Michael McMahon
2021-02-01 15:04 ` Ken Brown
2021-02-01 15:10 ` Corinna Vinschen
2021-02-07 19:35 ` Michael McMahon
2021-02-08 15:30 ` Ken Brown
2021-03-16 11:06 ` Sv: " sten.kristian.ivarsson
2021-03-16 13:00 ` Michael McMahon
2021-03-16 15:19 ` Ken Brown [this message]
2021-03-17 12:47 ` Sv: " sten.kristian.ivarsson
2021-03-17 15:47 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cc7931c-6c07-755d-2d0c-1b62189fddd9@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=michael.x.mcmahon@oracle.com \
--cc=sten.kristian.ivarsson@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).