Databases
StackOverflow2013
Postsdbo
POImageMagick on Mac OSX Snow Leopard. Is there any way to get it to compile and run?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POImageMagick on Mac OSX Snow Leopard. Is there any way to get it to compile and run?
    text
    copied!<p>It seems that I have more trouble getting standard Unix things to run on Snow Leopard than any other platform--including Windows cygwin</p> <p>For the past couple of days, I've been trying to get ImageMagick to run on Snow Leopard.</p> <p>The most obvious way, Mac Ports, fails:</p> <pre><code>tppllc-Mac-Pro:ImageMagick-sl swirsky$ sudo port install imagemagick ---&gt; Computing dependencies for p5-locale-gettext ---&gt; Configuring p5-locale-gettext Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-locale-gettext/work/gettext-1.05" &amp;&amp; /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: checking for gettext... no checking for gettext in -I/opt/local/include -arch i386 -L/opt/local/lib -lintl...gettext function not found. Please install libintl at Makefile.PL line 18. no Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade xorg-libXt failed Before reporting a bug, first run the command again with the -d flag to get complete output. tppllc-Mac-Pro:ImageMagick-sl swirsky$ </code></pre> <p>Not wanting to spend another two days figuring out why my libintl doesn't have a "gettext" function, I tried a different route: the script mentioned here: <a href="http://github.com/masterkain/ImageMagick-sl" rel="noreferrer">http://github.com/masterkain/ImageMagick-sl</a></p> <p>This script downloads and installs an ImageMagic independently of MacPorts issues</p> <pre><code>tppllc-Mac-Pro:ImageMagick-sl swirsky$ /usr/local/bin/convert dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib Referenced from: /opt/local/lib/libfontconfig.1.dylib Reason: Incompatible library version: libfontconfig.1.dylib requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0 Trace/BPT trap </code></pre> <p>It downloads everything and compiles fine, but fails when I try to run it, with the message above.</p> <p>So now I'm two steps away from ImageMagick, trying to get a newer libiconv on my machine.</p> <p>I downloaded the latest libiconv, compiled and built it. I put the resulting library in /opt/local/lib, and I still get the same error message:</p> <pre><code>tppllc-Mac-Pro:.libs swirsky$ sudo mv libiconv.2.dylib /opt/local/lib/libiconv.2.dylib tppllc-Mac-Pro:.libs swirsky$ convert dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib Referenced from: /opt/local/lib/libfontconfig.1.dylib Reason: Incompatible library version: libfontconfig.1.dylib requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0 Trace/BPT trap </code></pre> <p>Now here's something interesting. The error message shows it's looking in /opt/local/lib/libiconv.2.dylib. </p> <p>otools -L shows that this does implement 8.0.0:</p> <pre><code>tppllc-Mac-Pro:.libs swirsky$ otool -L /opt/local/lib/libiconv.2.dylib /opt/local/lib/libiconv.2.dylib: /usr/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.0) tppllc-Mac-Pro:.libs swirsky$ </code></pre> <p>And, for good measure, I set the DYLD_LIBRARY_PATH to make sure this directory is the one for dynamic libraries.</p> <p>So even though I do have a library that provides 8.0.0, it's being seen as 7.0.0! Any ideas why this would happen?</p> <p>So here's my question: Is it possible to get ImageMagick to run on OSX Snow Leopard? Are there any binary distributions that have static libraries baked in so I don't have to worry about these issue/</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload