On Feb 23 15:38, Andrew Schulman wrote:
> > > I see that bindresvport.c is part of the cygwin source code.
> >
> > You have apparently better eyes then I have. Where did you see that
> > bindresvport function in Cygwin?
> >
> > If you're talking about the implementation in newlib/libc/sys/linux/...
> > then it's unusable for Cygwin. There's a reason it's in the linux
> > subdirectory...
>
> Ah... ok.
>
> > > Would it be
> > > possible to have it exported from cygwin1.dll?
> >
> > No. We need a implementation which uses the limited functionality
> > of WinSock. It's not that hard, but it's definitely not going to be
> > in 1.5.20. http://cygwin.com/acronyms/#SHTDI
>
> OK, I'll have a look at it. Any ready pointers would be welcome.
bindresvport and bindresvport_sa are in functionality very similar to
rresvport, except that they don't create the socket by themselves. So,
actually it's fairly easy to implement bindresvport{_sa} by ripping out
the bigger part from rresvport, move it into its own function called
bindresvport_sa, and implementing bindresvport and rresvport by calling
bindresvport_sa.
Actually, I'm planning to do this anyway, but I already added too many
new functions to 1.5.20, so this must wait, same as getaddrinfo or our
own implementation of rexec/rcmd. However, this doesn't mean I wouldn't
be glad about help. You know, http://cygwin.com/acronyms/#PTC ;-)
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
