X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: bindresvport(): can it be exported from cygwin1.dll? Date: Thu, 23 Feb 2006 15:38:19 -0500 Lines: 20 Message-ID: References: <20060223201227 DOT GH4294 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > > 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. A. -- 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/