identify: unable to open module magick.la

Questions and postings pertaining to the development of ImageMagick, feature enhancements, and ImageMagick internals. ImageMagick source code and algorithms are discussed here. Usage questions which are too arcane for the normal user list should also be posted here.
Post Reply
User avatar
magick
Site Admin
Posts: 11100
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-05-03T17:27:57-07:00

We have magick.la and magick.so in the ImageMagick heirarchy on our Linux box. We'll check our Mac OS X box later and get back to you.

User avatar
magick
Site Admin
Posts: 11100
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-05-09T08:15:30-07:00

We cannot reproduce the problem you are having. We unpacked the binary distribution and set the execution path, MAGICK_HOME, and DYLD_LIBRARY_PATH. Next we typed
  • convert logo: logo.miff
    identify -verbose logo.miff
and it ran without complaint.

User avatar
magick
Site Admin
Posts: 11100
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-05-09T09:29:06-07:00

Are you getting the format list? We suspect the problem is it checks to see if there are any loadable modules and throws a warning exception. We probably should suppress the warning. Will fix within the next few days.

User avatar
magick
Site Admin
Posts: 11100
Joined: 2003-05-31T11:32:55-07:00

Post by magick » 2006-06-05T11:15:48-07:00

Add --without-modules to the configure script command line to inhibit modules from being built. We'll update the documentation. We did change the default because modules are more lightweight in that only modules that are used are loaded.

Post Reply