From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26928 invoked by alias); 5 Sep 2009 16:12:47 -0000 Received: (qmail 26920 invoked by uid 22791); 5 Sep 2009 16:12:46 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 05 Sep 2009 16:12:40 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 202FD6D4476; Sat, 5 Sep 2009 18:12:29 +0200 (CEST) Date: Sat, 05 Sep 2009 16:12:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: missing ipi_spec_dst in struct in_pktinfo Message-ID: <20090905161229.GA1869@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-09/txt/msg00150.txt.bz2 On Sep 4 16:10, Schulman.Andrew@epamail.epa.gov wrote: > > I'm trying to build socat for Cygwin (1.7). The build fails with > > xio-ip.c:480: error: structure has no member named `ipi_spec_dst' > > The offending code wants to use pktinfo->ipi_spec_dst.s_addr, where > pktinfo is a struct in_pktinfo *. The problem is that in Cygwin, > in_pktinfo doesn't have an ipi_spec_dst member. The IP man page > (http://homepages.cwi.nl/~aeb/linux/man2html/man7/ip.7.html) lists > in_pktinfo as > > struct in_pktinfo { > unsigned int ipi_ifindex; /* Interface index */ > struct in_addr ipi_spec_dst; /* Local address */ > struct in_addr ipi_addr; /* Header Destination address */ > }; > > while in /usr/include/cygwin/in.h, it's just > > struct in_pktinfo > { > struct in_addr ipi_addr; > uint32_t ipi_ifindex; > }; > > Any suggestions for a workaround to this problem? Why is ipi_spec_dst > missing, and more to the point, what can/should I substitute in its > place? ipi_spec_dst is missing because the Winsock structure in_pktinfo is defined without this field. The recvmsg function will return the Winsock equivalent to this structure, since that's how it gets it from Windows. The workaround is easy: Don't use that field. Disable the code in socat which uses it. Even if we would go to great lengths to add/remove the field when calling WSASendMsg/WSARecvMsg, it would be entirely meaningless anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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