Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Post the contents of libxml-2.0.pc. Also, provide the output of this command: ls /usr/include/libxml2. This info should be enough to determine why your build is failing.
Something has gone wrong with freetype as well (I could build 6.9.1-5 but not -6):
In file included from magick/annotate.c:82:0:
/home/glennrp/include/ft2build.h:56:38: fatal error: freetype/config/ftheader.h: No such file or directory
#include <freetype/config/ftheader.h>
The freetype problem seems to be due to configure now looking for "freetype/config/ftheader.h" instead of "freetype2/config/ftheader.h". That was easy to fix but now it's not finding libpng (i.e., why it's finding libpng12 not libpng16).... OK, it's because configure no longer looks for it; the PNG support in configure.ac has been simplified to the point that it doesn't work for me.
Last edited by glennrp on 2015-06-20T19:37:58-07:00, edited 1 time in total.
Not so much simplified as a move to the standard way of supporting packages now-a-days with pkg-config. The package.pc configuration file should provide all the information needed to link to a particular package. If that's not the case, we can always revert.
Ubuntu seems to not supply libpng.pc (or in fact any package.pc files). I can build OK with the system libpng (1.2.50) but not with a private libpng16 (which *does* have a libpng.pc). Using --with-pkgconfigdir=$HOME/lib/pkgconfig did not help; in that case IM is compiled with libpng16 but then attempts to link with libpng12 and fails.
The libxml-2.0.pc configuration file tells ImageMagick to look for parser.h in /usr/local/Cellar/libxml2/2.9.2/include/libxml2/parser.h. If the file is not there, the XML validation step will fail. If it find its, it then looks in /usr/local/Cellar/libxml2/2.9.2/lib for the XML library, libxml2.so. If it can't link to it, again the validation step fails and XML support is not available to ImageMagick. If these files exist elsewhere, you will need to edit libxml-2.0.pc to reflect their locations.