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 Date: Tue, 2 Apr 2002 10:21:00 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: inet_ntop support in cygwin? Message-ID: <20020402102100.C1475@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <5C97A373607ED31188CD002048406DEE070F0BA4 AT lsv-msg05 DOT stortek DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5C97A373607ED31188CD002048406DEE070F0BA4@lsv-msg05.stortek.com> User-Agent: Mutt/1.3.22.1i On Fri, Mar 29, 2002 at 02:16:33PM -0700, Harris, Jeffrey A wrote: > I just completed the install and download of all the packages of cygwin. > When compiling a program in cygwin I get the following.. > > gcc -g -Wall -c connect.c > connect.c: In function `lookup_host': > connect.c:26: warning: implicit declaration of function `inet_ntop' > connect.c:26: `INET_ADDRSTRLEN' undeclared (first use in this function) > connect.c:26: (Each undeclared identifier is reported only once > connect.c:26: for each function it appears in.) > connect.c: In function `connection_open': > connect.c:48: `INET_ADDRSTRLEN' undeclared (first use in this function) > connect.c:68: warning: implicit declaration of function `inet_pton' > connect.c:48: warning: unused variable `hostname' > make: *** [connect.o] Error 1 > > A search from / showed that the inet_ntop() function and INET_ADDRSTRLEN > define are not defined anywhere. Does cygwin support inet_ntop()? No INET6 support in Cygwin so far. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/