convert fails to find configure.xml
Posted: 2013-12-18T05:06:06-07:00
i installed the imgemagick binary from the image magick website following the instructions at http://imagemagick.org/script/binary-re ... php#macosx
when i try to run the convert program i get the following output:
$ convert -list configure
Path: [built-in]
Name Value
-------------------------------------------------------------------------------
FEATURES
NAME ImageMagick
QuantumDepth 16
convert: unable to access configure file `configure.xml' @ warning/configure.c/GetConfigureOptions/616.
i can see that the configure.xml file is installed:
$ find . -name configure.xml
./lib/ImageMagick-6.8.7/config-Q16/configure.xml
./share/doc/ImageMagick-6/www/source/configure.xml
my environment settings are as follows:
PATH=/Users/mainoo/IM/ImageMagick-6.8.7/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
DISPLAY=:0
DYLD_LIBRARY_PATH=/Users/mainoo/IM/ImageMagick-6.8.7/lib/
MAGICK_HOME=/Users/mainoo/IM/ImageMagick-6.8.7
i see that a similar issue was reported earlier this year (see link below) and a fix was applied - is this the same issue and if so, did the fix get ported to the mac binary?
viewtopic.php?f=3&t=23332
thanks
when i try to run the convert program i get the following output:
$ convert -list configure
Path: [built-in]
Name Value
-------------------------------------------------------------------------------
FEATURES
NAME ImageMagick
QuantumDepth 16
convert: unable to access configure file `configure.xml' @ warning/configure.c/GetConfigureOptions/616.
i can see that the configure.xml file is installed:
$ find . -name configure.xml
./lib/ImageMagick-6.8.7/config-Q16/configure.xml
./share/doc/ImageMagick-6/www/source/configure.xml
my environment settings are as follows:
PATH=/Users/mainoo/IM/ImageMagick-6.8.7/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
DISPLAY=:0
DYLD_LIBRARY_PATH=/Users/mainoo/IM/ImageMagick-6.8.7/lib/
MAGICK_HOME=/Users/mainoo/IM/ImageMagick-6.8.7
i see that a similar issue was reported earlier this year (see link below) and a fix was applied - is this the same issue and if so, did the fix get ported to the mac binary?
viewtopic.php?f=3&t=23332
thanks