Page 1 of 1

Core dump converting PNGs on Solaris using IM 6.3.6

Posted: 2008-01-04T03:52:42-07:00
by martinw17
Hi,

I have installed ImageMagick 6.3.6 11/22/07 Q16 from source on Solaris, using the standard options for configure.

The following command:
convert test-in.png test-out.png

Results in this error:
Assertion failed: image->signature == MagickSignature, file magick/blob.c, line 469

I get the same error if I try other simple operations using the command line tools such as identify, composite, etc.

Converting JPEGs works fine.

Is this an issue with lib dependencies? libpng-devel is installed (although I don't know which version).

Thanks,
Martin

Re: Core dump converting PNGs on Solaris using IM 6.3.6

Posted: 2008-01-07T17:11:23-07:00
by anthony
That is usally caused by a mismatch between the IM library and the coder modules, etc. Could you have two IM's installed?

Re: Core dump converting PNGs on Solaris using IM 6.3.6

Posted: 2008-01-08T09:04:24-07:00
by martinw17
Hi Antony,

Thanks for your response.

Actually I have: one installed to the default (/usr/local/) and another to /apps/ - I need to ensure that the new version (installed to /apps) works before I replace the old version in /usr/local (ironic that this is what's causing it to not work!)

I have done this loads of times on our Linux servers and both run fine side-by-side. Is this a Solaris issue?

Any tips for making it work? If need be I'll just install over the top of the old version to /usr/local.

Thanks,
Martin

Re: Core dump converting PNGs on Solaris using IM 6.3.6

Posted: 2008-01-08T18:09:31-07:00
by anthony
When you have two installed you MUST make sure the order of library loading and commands, cause it to use just one set of files and not the other.

I have had two versions of IM installed, without problems, once I had the PATH, LD_LIBRARY_PATH set correctly. The insalled position
should be correct for the compiled code so that the right coder modules are loaded for a specific library, and that means the non-system IM should have been compiled with the correct PREFIX configuration for the installation.


Alturnativally, you can build IM to install a specific NON-SYSTEM version of IM which uses a MAGICK_HOME environment variable to determine the PREFIX for the coder modules. (configure option --disable-installed)

See http://www.imagemagick.org/script/resources.php

Also my rough notes in http://www.cit.gu.edu.au/~anthony/info/ ... gick.hints