From owner-freebsd-ports@FreeBSD.ORG Mon Oct 15 14:48:17 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBB2416A417 for ; Mon, 15 Oct 2007 14:48:17 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id C02D213C465 for ; Mon, 15 Oct 2007 14:48:17 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 8825 invoked from network); 15 Oct 2007 14:48:17 -0000 Received: from aldan.algebra.com (HELO aldan-mlp) ([216.254.65.224]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Oct 2007 14:48:16 -0000 From: Mikhail Teterin To: David Southwell Date: Mon, 15 Oct 2007 10:48:14 -0400 User-Agent: KMail/1.7.1 References: <20071015120018.DB70C16A4A6@hub.freebsd.org> <200710150907.51692@aldan> <200710150739.08095.david@vizion2000.net> In-Reply-To: <200710150739.08095.david@vizion2000.net> Organization: Virtual Estates, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710151048.15066.mi+mill@aldan.algebra.com> Cc: freebsd-ports@freebsd.org Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64 openexr issues) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 14:48:17 -0000 =D0=CF=CE=C5=C4=A6=CC=CF=CB 15 =D6=CF=D7=D4=C5=CE=D8 2007 10:39 =C4=CF, Dav= id Southwell =F7=C9 =CE=C1=D0=C9=D3=C1=CC=C9: > 1. Any idea how long Module support will remain broken? This is a difficult question to answer, because it depends on the exact=20 configurations -- some modules are just fine, but some others mess things u= p,=20 when ImageMagick unloads them (via dlclose())... Jasper was a bad offender in the past, but I patched it a few weeks ago.=20 There, probably, remain other evil-doers :( That said, you do not need module support -- there is no gain from them.=20 Adding a third-party module (if any exists at all) remains possible even if= =20 ImageMagick's own modules are all linked in. > ** Makefile possibly broken: graphics/ImageMagick: > =9A =9A =9A =9A "Makefile", line 105: warning: OpenEXR's libIlmThread may= prevent > PerlMagick from working > =9A =9A =9A =9A "Makefile", line 108: warning: DjVu requires threads and = will not > be supported > =9A =9A =9A =9A ImageMagick-6.3.5.10_1 If you rebuilt the OpenEXR recently (be sure to read /usr/ports/UPDATING fo= r=20 details), you can ignore the OpenEXR warning. For DjVu it is, probably, bes= t=20 to just disable it -- it requires threads, which often make PerlMagick=20 unusable, because perl is not threaded by default on FreeBSD. Unless you know, you need DjVu support for something, PerlMagick is, probab= ly,=20 more important to you than DjVu... > As you can see I have two depencies not upgrading due to ImageMagick The warnings aren't supposed to trigger portupgrade's failure, but I rarely= =20 use the tool. There, likely, exists an option to cause it to try building t= he=20 port regardless... Yours, -mi