From owner-freebsd-ports@FreeBSD.ORG Sat Oct 13 20:44:36 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB18E44A for ; Sat, 13 Oct 2012 20:44:36 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 95F118FC08 for ; Sat, 13 Oct 2012 20:44:36 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q9DKiU1C068701; Sat, 13 Oct 2012 14:44:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q9DKiUWB068698; Sat, 13 Oct 2012 14:44:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 13 Oct 2012 14:44:30 -0600 (MDT) From: Warren Block To: Bob Willcox Subject: Re: The xpdf binary is MIA with xpdf-3.03_2 In-Reply-To: <20121013201848.GA3804@rancor.immure.com> Message-ID: References: <20121013201848.GA3804@rancor.immure.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sat, 13 Oct 2012 14:44:30 -0600 (MDT) Cc: ports list X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2012 20:44:36 -0000 On Sat, 13 Oct 2012, Bob Willcox wrote: > When building the xpdf port the xpdf executable is no longer being built or > installed into /usr/lib/libexec/xpdf. I suspect that this happened as the > result of a change that was made on 10/12/2012 with version xpdf-3.03_2. My > other systems that I've not updated the ports tree on lately have the > xpdf-3.03_1 version and there the executable is being built and istalled. > > Is anyone else seeing this (I have it failing on two of my recently ports tree > updated systems here)? Seen here also, sent off a message to the maintainer last night.