From: Michael McMahon <michael.x.mcmahon@oracle.com>
To: moss@cs.umass.edu
Cc: cygwin@cygwin.com
Subject: Re: Problems with native Unix domain sockets on Win 10/2019
Date: Fri, 25 Sep 2020 17:13:59 +0100 [thread overview]
Message-ID: <f6ebc8f3-d57e-3fd1-14db-8f231bdb39e0@oracle.com> (raw)
In-Reply-To: <35426eaa-56ac-ade8-10e1-9f4fd71db609@cs.umass.edu>
We're just trying to compile a test case and I checked that the
command line I sent does work. So, I think that it okay.
But, the original problem is with the Cygwin command line tools.
Michael.
On 25/09/2020 15:37, Eliot Moss wrote:
> Native Windows is not Cygwin ...
>
> If you have a problem in the native Windows environment, that would be
> with Microsoft, not Cygwin. If you're compiling for Cygwin, you need to
> use the CYgwin tool chain.
>
> Eliot Moss
next prev parent reply other threads:[~2020-09-25 16:16 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 [this message]
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
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=f6ebc8f3-d57e-3fd1-14db-8f231bdb39e0@oracle.com \
--to=michael.x.mcmahon@oracle.com \
--cc=cygwin@cygwin.com \
--cc=moss@cs.umass.edu \
/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).