From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19694 invoked by alias); 4 Sep 2009 21:09:22 -0000 Received: (qmail 19685 invoked by uid 22791); 4 Sep 2009 21:09:21 -0000 X-Spam-Check-By: sourceware.org Received: from pool-173-76-54-238.bstnma.fios.verizon.net (HELO cgf.cx) (173.76.54.238) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Sep 2009 21:09:14 +0000 Received: from ednor.cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id E58BC13C0C4 for ; Fri, 4 Sep 2009 17:09:04 -0400 (EDT) Received: by ednor.cgf.cx (Postfix, from userid 201) id DC2A52B35F; Fri, 4 Sep 2009 17:09:04 -0400 (EDT) Date: Fri, 04 Sep 2009 21:09:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: missing ipi_spec_dst in struct in_pktinfo Message-ID: <20090904210904.GA16028@ednor.casa.cgf.cx> 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.20 (2009-06-14) 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/msg00135.txt.bz2 On Fri, Sep 04, 2009 at 04:10:24PM -0400, 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? ip(7) says that "If ... ipi_spec_dst is not zero, then it is >used as the local source address for the routing table lookup and for >setting up IP source route options." This suggests that I could replace >it by zero. Comments? The structure isn't used by cygwin in any way so it sounds like you could replace it with whatever you want. cgf -- 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