[Octave-bug-tracker] [bug #49653] Build failure with ImageMagick

[John W. Eaton]

Update of bug #49653 (project octave):

                  Status:               Confirmed => Ready For Test         

    _______________________________________________________

Follow-up Comment #19:

Thanks for the changes.

It looks like the flags from pkg-config also provide the definitions of
MAGICKCORE_HDRI_ENABLE and MAGICKCORE_QUANTUM_DEPTH in CPPFLAGS, though on my
system they are repeated three times:


MAGICK_CPPFLAGS = -fopenmp -DMAGICKCORE_HDRI_ENABLE=0
-DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0
-DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0
-DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/x86_64-linux-gnu//ImageMagick-6
-I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu//ImageMagick-6
-I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu//ImageMagick-6
-I/usr/include/ImageMagick-6


Do you also have this?  It appears you are using an HDRI-enabled version.  Do
you have -DMAGICKCORE_HDRI_ENABLE=1 in CPPFLAGS and did you remove the
#defines that I added to the __magick_read__.cc file?  I would expect trouble
if the definition of MAGICKCORE_HDRI_ENABLE doesn't match the library you are
using.

Or maybe there is some other problem?  I now also see 6 imwrite.m test
failures and 4 more in jupyter-notebook/JupyterNotebook.tst.

For now, I pushed the following modified version of your change:

http://hg.savannah.gnu.org/hgweb/octave/rev/b7bce52e4500

Marking this report as ready for test.  If the build works, I think we should
close this report and open a separate one for failures when using
ImageMagick++ instead of GraphicsMagick++.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49653>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/