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:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; q=dns; s=default; b=dYvVlLtQkQmUI05z3I5tiH4cYrivnB0llbFHKJz7+9u YyQZtfNiOvBzZMAzUqM1cfmm+9WP7Hb3QCn9BTuC0/eM8LJWjVf4n1guOHtv/VYE Wy+fhCgv0UFBr83vRwbU9qWrw1cipmv2y/dDU0kwc+Yx2ZDa9Jmf5+fTiqUEqWfQ = 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:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; s=default; bh=7f2T4M5djKexs7QjQLWhlBb5irk=; b=XiULZklnso/3PtPAe pAkg+IrkPDVAXyDcr9tnPww59LkgRTcOezQsjBvIdtrWi1GzyKOhrQP2WX6kN+he OtmITaRMsR9jGplfzX4hJ7ksYPty5foFSZVwkAT4TNJSAvJQ6XqtpFUkUn5qz9Yl W6cj2zdhJFSLQQcmydDjlKRNmY= 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=-0.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_SORBS_DUL,SPF_PASS autolearn=ham version=3.3.2 X-HELO: conuserg004-v.nifty.com X-Nifty-SrcIP: [121.93.68.199] Date: Thu, 21 May 2015 20:15:09 +0900 From: Takashi Yano To: cygwin AT cygwin DOT com Subject: Re: cannot build cygwin-2.0.2 because of net.cc (or because of some header.h) Message-Id: <20150521201509.9b9bfcffb07b3d9337de9e10@nifty.ne.jp> In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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. -- 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