Re^3: Image::Magick - Exception 435: unable to open file `Image::Magick::Q16' @ error/Q16.xs/XS_Image__Magick__Q16

Hmm, I had a little dig, and I'm not getting very far: the internal structure of the code is, um, unusual. You are probably best off opening an issue on github, but be warned that the maintainers are a small team that appear to be somewhat swamped.

I note that you have not mentioned the version of perl: they will likely want that alongside the other version numbers you have mentioned.

Comment on Re^3: Image::Magick - Exception 435: unable to open file `Image::Magick::Q16' @ error/Q16.xs/XS_Image__Magick__Q16_Read/13529

Replies are listed 'Best First'.
Re^4: Image::Magick - Exception 435: unable to open file `Image::Magick::Q16' @ error/Q16.xs/XS_Image__Magick__Q16_Read/13529 by mldvx4 (Hermit) on Jun 08, 2023 at 15:23 UTC
Thanks. After starting to check some semi-random things, I found that once I added imagemagick-svg and imagemagick-webp to that system the script resumed working. So, at the end of the day, the problem had nothing to do with Perl except that the symptoms of some change manifested via well-used Perl script on a production system which has only received system updates of late. Unfortunately I have no clue as to what or why there were changes inside those updates which set the script off its rails. tldr; solved but dunno the original cause	[reply]

Replies are listed 'Best First'.

Re^4: Image::Magick - Exception 435: unable to open file `Image::Magick::Q16' @ error/Q16.xs/XS_Image__Magick__Q16_Read/13529
by mldvx4 (Hermit) on Jun 08, 2023 at 15:23 UTC

Thanks. After starting to check some semi-random things, I found that once I added imagemagick-svg and imagemagick-webp to that system the script resumed working. So, at the end of the day, the problem had nothing to do with Perl except that the symptoms of some change manifested via well-used Perl script on a production system which has only received system updates of late. Unfortunately I have no clue as to what or why there were changes inside those updates which set the script off its rails.

tldr; solved but dunno the original cause

[reply]