On Jan 19 08:48, Henri wrote:
> Corinna Vinschen cygwin.com> writes:
> > On Jan 18 18:10, Henri wrote:
> > > Corinna Vinschen cygwin.com> writes:
> > >
> > > > There's no firewall involved if a simple socket call goes wrong.
> > > > For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbou
Corinna Vinschen cygwin.com> writes:
>
> On Jan 18 18:10, Henri wrote:
> > Corinna Vinschen cygwin.com> writes:
> >
> > > There's no firewall involved if a simple socket call goes wrong.
> > > For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbound
> > > until you call bind or connec
On Jan 18 18:10, Henri wrote:
> Corinna Vinschen cygwin.com> writes:
>
> > There's no firewall involved if a simple socket call goes wrong.
> > For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbound
> > until you call bind or connect.
>
> s/AF_INET/AF_UNIX/ ? (sorry for my intrusi
Corinna Vinschen cygwin.com> writes:
> There's no firewall involved if a simple socket call goes wrong.
> For AF_LOCAL Cygwin opens an AF_INET socket, but which is unbound
> until you call bind or connect.
s/AF_INET/AF_UNIX/ ? (sorry for my intrusion)
Regards,
Henri
--
Problem reports:
On Jan 16 18:16, Glen L wrote:
>
> Greetings all,
>
> I'm moving a "C" program to 64-bit Windows 10 that worked previously
> in 32-bit Win7. It builds, compiles and runs (AFAIK) with the
> exception of being able to open a socket. Calling the socket thusly:
>
> if ((g->listen = socket(PF_LOC
5 matches
Mail list logo