From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: AF_HYPERV address family not supported
Date: Thu, 04 Jul 2019 18:50:00 -0000 [thread overview]
Message-ID: <4c32d33c-eab3-c031-52dd-c7ca7ab050f4@SystematicSw.ab.ca> (raw)
In-Reply-To: <CALK-3mKwcNXkhn5GxKc0r=3seOM5S7jx3_L8CkjSkxd9qVE-=g@mail.gmail.com>
On 2019-07-04 11:23, Biswapriyo Nath wrote:
> Here is the sample code that I've tried.
>
> #include <sys/socket.h>
> #include <stdio.h>
> #include <errno.h>
>
> #ifndef AF_HYPERV
> #define AF_HYPERV 34
> #endif
>
> int main(void)
> {
> int s = socket(AF_HYPERV, SOCK_STREAM, 0);
> if (s > 0)
> printf("success\n");
> else
> printf("%s\n", strerror(errno));
> }
>
> Is this by-design? Or am I doing anything wrong?
That's a Windows API - the Linux equivalent is AF_VSOCK: please feel free to
submit support patches to cygwin-patches to support AF_VSOCK using AF_HYPERV or
newlib to support AF_VSOCK.
https://cygwin.com/acronyms/#SHTDI
You could check to see if the Windows oriented mingw or msys projects support
AF_HYPERV yet.
These interfaces are fairly new and OS specific so there is not yet a facility
abstraction to support.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
next prev parent reply other threads:[~2019-07-04 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 17:23 Biswapriyo Nath
2019-07-04 18:50 ` Brian Inglis [this message]
2019-07-10 18:41 ` Biswapriyo Nath
2019-07-10 21:52 ` Brian Inglis
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=4c32d33c-eab3-c031-52dd-c7ca7ab050f4@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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).