X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=OuepKTaQYgxiQY/RFpIg4o27ugUzoFpu893ct6LN1G2 WUgt8rl2H+/KNMjw1QEWGV8mJwszoaeNxZOdiww/0XRYau316ho5jO7TbZkwwQhv /mPXj8hT2tu33uqE1/7Q73xSraiJganRs4nnXyabNYbrrrZcrUwxg8e+qrdHJuEY = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=y+fGup8r9hl0CRtCkGj6Qoqc0v8=; b=wQlgDnbiR03aAOMXM QisNQurXjg1BlTzs27C68wiD6CCBM8ptULjM9DNTJwrIihhVPN2LqspnRAi6QVH7 9xPaYO1/VIoRlfNiKmWa8NX5Nqx2VQJcOvX/ZnbSnY4rGtUn/vjnUpDyWFVGLD/H FhWEsO9jGlJkmep/D/8w0F9mfA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: etr-usa.com Message-ID: <52D9A0C9.4080508@etr-usa.com> Date: Fri, 17 Jan 2014 14:29:45 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Cygwin-L Subject: Re: socat with IP6 support? References: <52D985D3 DOT 9070506 AT etr-usa DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 1/17/2014 13:45, Aaron Humphrey wrote: > > So why does it think it > requires ip6.h if it compiles fine without it? It's probably an unwarranted Linuxism. As I read POSIX[*], it is legal to have IPv6 definitions in the same old headers the IPv4 interface is defined in, as Cygwin does. So, three choices: 1. Cygwin could add stub headers for these to placate socat and any other software that uses their presence as an IPv6 test; or 2. Someone can lobby socat to fix their test; or 3. The socat package maintainer can patch the software before building it. If it were me, I'd first try diddling config.h after the configure script generates it, rather than hack the configure script itself. If that works, it's a one-line fix. [*] http://goo.gl/lMIJUK -- 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