ImageMagick build fails on Snow Leopard when cryptlib is active

[jwhowse4@…]

On an Intel Mac running Snow Leopard 10.6.2, an upgrade from ImageMagick 6.5.8 to 6.5.9 fails with the following error message. Attached is a more detailed output collected using the debug flag. Any ideas what is going wrong?

checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for working volatile... yes
checking for preprocessor stringizing operator... yes
checking whether stat file-mode macros are broken... no
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking whether #! works in shell scripts... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for C/C++ restrict keyword... __restrict
checking whether byte ordering is bigendian... no
checking for mode_t... yes
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking for long double with more range or precision than double... yes
checking whether char is unsigned... no
checking size of signed short... 0
checking size of unsigned short... 0
checking size of signed int... 0
checking size of unsigned int... 0
checking size of signed long... 0
checking size of unsigned long... 0
checking size of signed long long... 0
checking size of unsigned long long... 0
checking size of off_t... configure: error: in `/opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_graphics_ImageMagick/work/ImageMagick-6.5.9-0':
configure: error: cannot compute sizeof (off_t)
See `config.log' for more details.
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/macports/var/macports/build/_opt_macports_var_macports_sources_rsync.macports.org_release_ports_graphics_ImageMagick/work/ImageMagick-6.5.9-0" && ./configure --prefix=/opt/macports --enable-shared --enable-static --disable-ltdl-install --with-frozenpaths --without-openexr --disable-hdri --with-dps --with-bzlib --with-fontconfig --with-jpeg --with-png --with-tiff --with-zlib --with-modules --with-xml --with-x --without-fpx --without-lqr --with-rsvg --with-perl=/opt/macports/bin/perl --with-gslib --with-lcms --with-wmf --with-jbig --with-jp2 --with-gvc --with-quantum-depth=32 " returned error 77
Warning: the following items did not execute (for ImageMagick): org.macports.destroot org.macports.configure org.macports.build

[jwhowse4@…]

Debug Output

[jmr@…]

Please remember to fill in the Port field and cc the maintainer.

Something is seriously wrong with your system; attach the config.log.

[jwhowse4@…]

Configure Log

[jwhowse4@…]

Replying to jmr@…:

Please remember to fill in the Port field and cc the maintainer.

Something is seriously wrong with your system; attach the config.log.

Strange that I have not noticed anything previously. The config.log is attached. Thanks for your help.

[ryandesign@…]

ImageMagick seems to (now) have a conflict with cryptlib. It's using the flag "-lCL" presumably to link with Apple's OpenCL, but on case-insensitive systems like Mac OS X, cryptlib's "libcl.dylib" matches this, and since that's not the library it was looking for, it mucks things up.

You can work around this by deactivating cryptlib, cleaning ImageMagick, upgrading ImageMagick, and then, if desired, reactivating cryptlib.

sudo port deactivate cryptlib
sudo port clean ImageMagick
sudo port upgrade ImageMagick
sudo port activate cryptlib

I added a check for this to ImageMagick in r62884. I should also see if this has already been reported to the developers.

[jwhowse4@…]

Replying to ryandesign@…:

ImageMagick seems to (now) have a conflict with cryptlib. It's using the flag "-lCL" presumably to link with Apple's OpenCL, but on case-insensitive systems like Mac OS X, cryptlib's "libcl.dylib" matches this, and since that's not the library it was looking for, it mucks things up.

You can work around this by deactivating cryptlib, cleaning ImageMagick, upgrading ImageMagick, and then, if desired, reactivating cryptlib.

sudo port deactivate cryptlib
sudo port clean ImageMagick
sudo port upgrade ImageMagick
sudo port activate cryptlib

I added a check for this to ImageMagick in r62884. I should also see if this has already been reported to the developers.

This solution worked for me. Thanks for tracking this down.

[ryandesign@…]

r97532