From owner-freebsd-ports@FreeBSD.ORG Tue Oct 16 07:55:52 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 5FEA716A419 for ; Tue, 16 Oct 2007 07:55:52 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3048D13C455 for ; Tue, 16 Oct 2007 07:55:51 +0000 (UTC) (envelope-from david@vizion2000.net) Received: by dns1.vizion2000.net (Postfix, from userid 1007) id 504E41CC4C; Tue, 16 Oct 2007 01:12:56 -0700 (PDT) Content-Disposition: inline From: David Southwell Organization: Voice and Vision To: freebsd-ports@freebsd.org Date: Tue, 16 Oct 2007 01:12:55 -0700 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200710160112.56089.david@vizion2000.net> Subject: Fwd: 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: Tue, 16 Oct 2007 07:55:52 -0000 =2D--------- Forwarded Message ---------- Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -am= d64=20 openexr issues) Date: Tuesday 16 October 2007 =46rom: David Southwell To: Mikhail Teterin On Monday 15 October 2007 07:48:14 you wrote: > =D0=BF=D0=BE=D0=BD=D0=B5=D0=B4=D1=96=D0=BB=D0=BE=D0=BA 15 =D0=B6=D0=BE=D0= =B2=D1=82=D0=B5=D0=BD=D1=8C 2007 10:39 =D0=B4=D0=BE, David Southwell =D0=92= =D0=B8 =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB=D0=B8: > > 1. Any idea how long Module support will remain broken? > > This is a difficult question to answer, because it depends on the exact > configurations -- some modules are just fine, but some others mess things > up, when ImageMagick unloads them (via dlclose())... > > Jasper was a bad offender in the past, but I patched it a few weeks ago. > There, probably, remain other evil-doers :( > > That said, you do not need module support -- there is no gain from them. > Adding a third-party module (if any exists at all) remains possible even = if > ImageMagick's own modules are all linked in. > > > ** Makefile possibly broken: graphics/ImageMagick: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "Makefile", line 105: warning: OpenEXR's li= bIlmThread may prevent > > PerlMagick from working > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "Makefile", line 108: warning: DjVu require= s threads and will not > > be supported > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 ImageMagick-6.3.5.10_1 > > If you rebuilt the OpenEXR recently (be sure to read /usr/ports/UPDATING > for details), you can ignore the OpenEXR warning. For DjVu it is, probabl= y, > best to just disable it -- it requires threads, which often make PerlMagi= ck > unusable, because perl is not threaded by default on FreeBSD. What is the situation when perl is comliled with threads? Is ImageMagick's= =20 Makefile intenmded to cope with that? > > Unless you know, you need DjVu support for something, PerlMagick is, > probably, 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 rare= ly > use the tool. There, likely, exists an option to cause it to try building > the port regardless... How about a patch for the makefile? > > Yours, > > -mi Thanks for all your help -- it is appreciated David =2D------------------------------------------------------