Date: Tue, 16 Oct 2007 01:30:21 -0700 From: David Southwell <david@vizion2000.net> To: freebsd-ports@freebsd.org Subject: Re: Fwd: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure -amd64 openexr issues) Message-ID: <200710160130.21714.david@vizion2000.net> In-Reply-To: <200710160112.56089.david@vizion2000.net> References: <200710160112.56089.david@vizion2000.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 16 October 2007 01:12:55 David Southwell wrote: > ---------- Forwarded Message ---------- > > Subject: Re: ImageMagick modules (Re: ImageMagick - portupgrade failure > -amd64 openexr issues) > Date: Tuesday 16 October 2007 > From: David Southwell <david@vizion2000.net> > To: Mikhail Teterin <mi+mill@aldan.algebra.com> > > 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 thin= gs > > 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 = libIlmThread may > > > prevent PerlMagick from working > > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 "Makefile", line 108: warning: DjVu requi= res 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, > > probably, best to just disable it -- it requires threads, which often > > make PerlMagick unusable, because perl is not threaded by default on > > FreeBSD. > > What is the situation when perl is comliled with threads? Is ImageMagick's > 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 > > rarely 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 > Just a further point the maintainer of OpenEXR seems to be suggesting that = the=20 warning in regard to OpenEXR may be out of date.. perhaps ImageMagick's=20 Makefile needs some modification in the light of the recent changes to=20 OpenEXr.. (I am not puttimng myselkf up as an authority here -- I no sweet= =20 =46A<chuckles>. Also perl on my system is compiled with threads but ImageMagick does not se= em=20 to realise that or should it be told explicitly?=20 David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710160130.21714.david>