From owner-freebsd-ports@FreeBSD.ORG Sun Nov 10 03:12:56 2013 Return-Path: Delivered-To: freebsd-ports@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 098CA8DE for ; Sun, 10 Nov 2013 03:12:56 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2F662291 for ; Sun, 10 Nov 2013 03:12:55 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id rAA3CsLq075713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 9 Nov 2013 19:12:54 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id rAA3CsVw075712 for freebsd-ports@freebsd.org; Sat, 9 Nov 2013 19:12:54 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA18176; Sat, 9 Nov 13 18:59:14 PST Date: Sat, 09 Nov 2013 19:00:23 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: freebsd-ports@freebsd.org Subject: opvp support seems broken in ghostscript port Message-Id: <527ef6c7.+FAIJps4aSBVGYtm%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Sun, 10 Nov 2013 03:12:56 -0000 Has anyone been able to use the opvp support in ghostscript? It works fine displaying to the screen, but when I specify -sDEVICE=opvp I get **** Unable to open the initial device, quitting. If I also specify -dINITDEBUG=1 (which turns on debug output in the initialization file, gs_init.ps) I get a lot of messages showing progress through the initialization process -- none of which seem to have anything to do with device choice, nor to be much different from what INITDEBUG produces when displaying to the screen -- until END FONTS 219 2605656 1227805 1417680 125870 true 1166 4 <0> Unrecoverable error: unknownerror in setdevice Operand stack: --nostringval-- which is not a whole lot more informative than the original message. (When displaying to the screen, the next line after "END FONTS ..." is "END DEVICE ...") Is there any way to turn on debug or tracing, or otherwise get more detail, re what is going on in setdevice and exactly what failed? So far I haven't found anything particularly helpful using Google.