Date: Thu, 18 May 2000 08:26:39 +0200 (CEST) From: lkoeller@cc.fh-lippe.de To: FreeBSD-gnats-submit@freebsd.org Subject: ports/18644: hylafax and libtiff-3.4 Message-ID: <200005180626.IAA86126@odie.lippe.de>
next in thread | raw e-mail | index | archive | help
>Number: 18644 >Category: ports >Synopsis: hylafax and libtiff-3.4 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu May 18 00:10:02 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Lars Koeller >Release: FreeBSD 3.4-RELEASE i386 >Organization: Fachhochschule Lippe, Lemgo, Germany >Environment: FreeBSD-3.4 RELEASE i386 with up to date ports tree. >Description: First the hylafax port needs to be updated, but thats not the point. Even the newest hylafax version states to work only correctly with tifflib-3.4! This lib isn't available in the ports tree, and using libtiff-3.5 with hylafax leads to nonfunction progs, which consuming all of the CPU time if started. The conversion programs from tiff-3.5 runs well, but the lib must be 3.4. So it would be necessary to reaktivate the latest libtiff-3.4 port for having a chance to get a running hylafax. >How-To-Repeat: Build hylafax and test it. It won't run. >Fix: Update hylafax and make it using libtiff-3.4. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005180626.IAA86126>