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 :content-type:content-transfer-encoding; q=dns; s=default; b=hFu FqQOqvqlWwsrWPcNSGc1UAAhHkxIfE++HFChvEVkSUVVqKLC82hbtXXkRlmaZmHp xMl1t0ACEvroFe0lbRoW+1FspamAFtaN9qaJQL6ERjCAwCuhGtVSEKbfAzzPGUXi 6JNq2anWhlgC/TLOfWB2PJAMsUtBhsx/DrJcyN3k= 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 :content-type:content-transfer-encoding; s=default; bh=1XqGYl805 krYuPRPNU4kA7rYdio=; b=FQ0HgwY5ckvHMko1IrdwWRaqtDQySPnN2EBgUbzCE tNuHgk+BkPgGoHAuFqbQTX8xYxru83mw0F5ZZ5zembAv0L3O57/UOxNrjJSIaPc5 1pM1dzyL7YL8HH+9iDzMFZfns69VsURR25JDK9pY3GDIj0sY96faEQoIpOEvlQ07 sI= 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,RCVD_IN_BRBL_LASTEXT,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail.lysator.liu.se Message-ID: <5384368E.4000707@lysator.liu.se> Date: Tue, 27 May 2014 08:54:06 +0200 From: Peter Rosin User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: libtirpc and redeclared bindresvport/bindresvport_sa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi! I ran into this problem [1] when doing some RPC coding, and went searching for a resolution. But I came up empty. Was there any further discussion? Is this what is holding up the libvirt ITP? I guess the window for releasing an ABI-incompatible libtirpc 0.2.1-2 is firmly closed. Meanwhile, libtirpc-0.2.4 has been released, but this particular problem probably remains [2]. Cheers, Peter [1] https://cygwin.com/ml/cygwin/2010-08/msg00659.html [2] http://sourceforge.net/p/libtirpc/bugs/23/ -- 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