From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22169 invoked by alias); 22 May 2015 10:37:31 -0000 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 Received: (qmail 22151 invoked by uid 89); 22 May 2015 10:37:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_20,RCVD_IN_SORBS_DUL,SPF_PASS autolearn=ham version=3.3.2 X-HELO: conuserg006-v.nifty.com Received: from conuserg006.nifty.com (HELO conuserg006-v.nifty.com) (202.248.45.248) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (DES-CBC3-SHA encrypted) ESMTPS; Fri, 22 May 2015 10:37:27 +0000 Received: from Express5800-S70 (ntsitm305199.sitm.nt.ftth.ppp.infoweb.ne.jp [121.93.68.199]) (authenticated) by conuserg006-v.nifty.com with ESMTP id t4MAb3fv027641 for ; Fri, 22 May 2015 19:37:04 +0900 X-Nifty-SrcIP: [121.93.68.199] Date: Fri, 22 May 2015 11:07:00 -0000 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: cannot build cygwin-2.0.2 because of net.cc (or because of some header.h) Message-Id: <20150522193704.b0b9dfdaa4d63c61d7d5be55@nifty.ne.jp> In-Reply-To: <20150521201509.9b9bfcffb07b3d9337de9e10@nifty.ne.jp> References: <20150521201509.9b9bfcffb07b3d9337de9e10@nifty.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00304.txt.bz2 On Thu, 21 May 2015 20:15:09 +0900 Takashi Yano wrote: > On Mon, 11 May 2015 17:52:04 +0200 > Denis Excoffier wrote: > > > In order to successfully build cygwin-2.0.2-1 (for x86, both XP and W7) i had to apply > > the following patch (below). No such problem with cygwin-2.0.1-1. > > In my case, the same problem is caused by upgrading > w32api-headers to 4.0.2-1. It does not result from > difference between cygwin-2.0.2-1 and cygwin-2.0.1-1. I have looked into this problem. The cause is as follows. netioapi.h in w32api-headers 3.3.0-2 was using a macro-name _INC_NETIOAPI for include-guard. By defining _INC_NETIOAPI, net.cc avoids including netioapi.h, which conflicts with if_nametoindex() and if_indextoname() in it. However, the macro-name for include-guard in netioapi.h of w32api-headers 4.0.2-1 has been changed to _NETIOAPI_H_. As a result, net.cc fails to avoid including netioapi.h, which causes confliction. Thus, defining _NETIOAPI_H_ in net.cc resolves the problem. diff --git a/winsup/cygwin/net.cc b/winsup/cygwin/net.cc index eaf6eb8..d6a631b 100644 --- a/winsup/cygwin/net.cc +++ b/winsup/cygwin/net.cc @@ -19,6 +19,7 @@ details. */ TODO: Convert if_nametoindex to cygwin_if_nametoindex and call system functions on Vista and later. */ #define _INC_NETIOAPI +#define _NETIOAPI_H_ #include "winsup.h" #ifdef __x86_64__ /* 2014-04-24: Current Mingw headers define sockaddr_in6 using u_long (8 byte) -- Takashi Yano -- 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