From: Biswapriyo Nath <nathbappai@gmail.com>
To: cygwin@cygwin.com
Subject: AF_HYPERV address family not supported
Date: Thu, 04 Jul 2019 17:23:00 -0000 [thread overview]
Message-ID: <CALK-3mKwcNXkhn5GxKc0r=3seOM5S7jx3_L8CkjSkxd9qVE-=g@mail.gmail.com> (raw)
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?
--
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 reply other threads:[~2019-07-04 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 17:23 Biswapriyo Nath [this message]
2019-07-04 18:50 ` Brian Inglis
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='CALK-3mKwcNXkhn5GxKc0r=3seOM5S7jx3_L8CkjSkxd9qVE-=g@mail.gmail.com' \
--to=nathbappai@gmail.com \
--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).