From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Sep 12 18:30:01 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 64BE943B for ; Thu, 12 Sep 2013 18:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 51D732808 for ; Thu, 12 Sep 2013 18:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r8CIU15R038931 for ; Thu, 12 Sep 2013 18:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r8CIU03R038930; Thu, 12 Sep 2013 18:30:00 GMT (envelope-from gnats) Date: Thu, 12 Sep 2013 18:30:00 GMT Message-Id: <201309121830.r8CIU03R038930@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: kaltheat@googlemail.com Subject: Re: ports/182025: net/tigervnc can't be built after upgrade of port to 1.3.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: kaltheat@googlemail.com List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 18:30:01 -0000 The following reply was made to PR ports/182025; it has been noted by GNATS. From: kaltheat@googlemail.com To: Koichiro IWAO Cc: bug-followup@freebsd.org, kaltheat@gmail.com Subject: Re: ports/182025: net/tigervnc can't be built after upgrade of port to 1.3.0 Date: Thu, 12 Sep 2013 19:34:14 +0200 I just rechecked. I'm working on HEAD of portstree (Revision 327087). I did: # cd /usr/ports/net/tigervnc && make fetch extract patch # find work -exec grep "if XORG " {} + work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncExtInit.cc:#if XORG < 112 ... work/tigervnc-1.3.0/unix/xserver/hw/vnc/xf86vncModule.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/xf86vncModule.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG < 110 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG == 15 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#elif XORG < 19 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG < 110 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG >= 16 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG < 112 work/tigervnc-1.3.0/unix/xserver/hw/vnc/vncHooks.cc:#if XORG < 19 ... This supports the conclusion that the mentioned patch is not included. Regards, kaltheat