Imagemagick build fails.

dk88

New member
Joined
Feb 10, 2022
Messages
3
I have a bunch os servers still running on Centos 6.10 with custombuild version 2.0.0. We upgrade these servers once a month using an ansible playbook, this has been running for a few years without major problems. However in the last updates imagemagick is having problems compiling.

Here is a snippet of the build output, the full output is attached as a txt and I also included the options.conf.

Code:
# ./build imagemagick
...
...
...
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-viff.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-vips.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-wbmp.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-wpg.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xbm.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xc.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xcf.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xpm.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xps.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-xtrn.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-yaml.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-ycbcr.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-yuv.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-jpeg.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-png.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-ept.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-tiff.lo
  CC       coders/MagickCore_libMagickCore_7_Q16HDRI_la-webp.lo
coders/tiff.c:2938: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'TIFFWritePixels'
coders/tiff.c: In function 'TIFFSetProfiles':
coders/tiff.c:3178: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
coders/tiff.c:3178: error: 'field' undeclared (first use in this function)
coders/tiff.c:3178: error: (Each undeclared identifier is reported only once
coders/tiff.c:3178: error: for each function it appears in.)
coders/tiff.c:3191: warning: implicit declaration of function 'TIFFFieldDataType'
coders/tiff.c: In function 'WriteTIFFImage':
coders/tiff.c:3977: warning: implicit declaration of function 'TIFFWritePixels'
make[1]: *** [coders/MagickCore_libMagickCore_7_Q16HDRI_la-tiff.lo] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/usr/local/directadmin/custombuild/ImageMagick-7.1.0-19'
make: *** [all] Error 2

Customer support redirected me to the forum as they are backlogged. Has anyone run into similar problems?
 

Attachments

Maybe this helps
 
Maybe this helps
Thanks, I tried running "ldconfig /usr/local/lib64/" but no dice. As far as I know ldconfig is only responsible for linking shared objects dynamically, for example Apache wants to use part of imagemagick and the ldconf will tell the application where to find it.

My problem occurs during compiling of the program and to me (, I am no programmer), looks like a syntax error. This can have many causes, but most likely an invalid combination of options in the options.conf, outdated OS/compiler or even a typo in the imagemagick source files. So I am hoping there are other users with similar issues.
 
Not sure if you still need help but I have seen the same issue on an older CentOS 6 server that wouldn't build ImageMagick 7.1.0-24.

It seems to go wrong with the libtiff library, If these are installed then ImageMagick will try to build itself with TIFF image support and this fails with the errors you showed in your first post. If you don't need TIFF image support than a solution is rather simpel, delete the tiff libraries.

Code:
yum remove libtiff.x86_64 libtiff-devel.x86_64

Might not be ideal for everyone but it worked for me.
 
Yes, thank you, we will definitely try this!

For now we have decided to migrate these websites to new servers, however that is a slow process and they expect this will take about 6 months. The OS updates for Centos 6.x have been stopped for a while, so having the DirectAdmin services be up to date is important to us.
 
Back
Top