ryandesign at macports.org
Fri Aug 1 16:03:51 PDT 2008
On Aug 1, 2008, at 12:47, David Liontooth wrote:
> Ryan Schmidt wrote:
>> On Aug 1, 2008, at 01:19, David Liontooth wrote:
>>> I'm enclosing the portfile for transcode 1.1.0 beta0, in which
>>> the link to the new ImageMagick libraries has been fixed -- the
>>> port may require a recent version of ImageMagick.
>>> The portfile works on Intel iMacs with 10.5.4 using
>>> port install transcode +a52dec +faac +freetype +imagemagick
>>> +libdv +libogg +libsdl +libtheora +libvorbis +libxml2 +x264 +xvid
>> I committed your new portfile in r38879, except that I also
>> removed the "revision 1" line, since every new version of a port
>> should begin at revision 0.
> Thanks. I did some further testing and it appears the ImageMagick
> libraries are still not linked correctly -- we still need this
> cd /opt/local/lib
> ln -s libMagickCore.1.dylib libMagick.dylib
> Older versions of ImageMagick work without the workaround; not sure
> which version introduces the change from "libMagick" to
libMagick changed names to libMagickCore in ImageMagick 6.3.8-5. See
the ImageMagick change log. Programs should not assume that the
library is called libMagick or libMagickCore; they should use "Magick-
config --libs" or "pkg-config ImageMagick --libs" to determine how to
link with the library.
> I've confirmed the beta0 version also builds on PPC, but it needs
> the workaround with recent versions of ImageMagick.
> I'm cc'ing upstream -- Francesco, I don't know what's happening
> here, but the linking is still not working for the new ImageMagick.
>> May I also add "use_parallel_build yes" to the port? It appears to
>> work fine with that option and makes it compile faster on
>> multicore machines.
> My co-maintainer may have reservations on these changes; I regret
> we haven't been able to sort out the linking issues yet.
More information about the macports-users