Bug 710528 – sci-mathematics/octave-5.1.0 - does not find ImageMagick++

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Sławomir Nizio 2020-02-22 20:52:02 UTC]

This is similar to bug 656730. I hacked it this way:

diff --git a/sci-mathematics/octave/octave-5.1.0.ebuild b/sci-mathematics/octave/octave-5.1.0.ebuild
index d70fbe73a..ccc60fdb2 100644
--- a/sci-mathematics/octave/octave-5.1.0.ebuild
+++ b/sci-mathematics/octave/octave-5.1.0.ebuild
@@ -137,7 +137,7 @@ src_configure() {
                $(use_enable fftw fftw-threads) \
                $(use_with glpk) \
                $(use_with hdf5) \
-               $(use_with imagemagick magick $(usex graphicsmagick GraphicsMagick ImageMagick)) \
+               $(use_with imagemagick magick $(usex graphicsmagick GraphicsMagick Magick)) \
                $(use_with opengl) \
                $(use_with opengl fltk) \
                $(use_with ssl openssl) \


Testing on the way.

sci-mathematics/octave-5.1.0 with USE=imagemagick
media-gfx/imagemagick-7.0.9.16

Reproducible: Always

[Comment 1 Sławomir Nizio 2020-02-22 20:52:41 UTC]

error print:

configure: WARNING: ImageMagick++ library not found.  The imread, imwrite, and imfinfo functions for reading and writing image files will not be fully functional.

[Comment 2 Jonas Stein 2020-02-22 21:01:34 UTC]

Thank you for the report. Please recompile and 
*attach* the logfiles and 
paste the emerge info as described on
https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket
We need to have all information at hand before ticket assignment, so that the maintainer can look after it in one session with minimal number of callbacks.
Please reopen this ticket (Status:unconfirmed) afterwards.

[Comment 3 Sławomir Nizio 2020-02-22 21:04:27 UTC]

The fix seems to work (no such print anymore; runtime not tested), although it's kind of hacky, deduced (according to help strings in configure, the string should be ImageMagick).

new log:

checking Magick++.h usability... yes
checking Magick++.h presence... yes
checking for Magick++.h... yes
checking for Magick::ColorRGB in Magick++.h... yes

[Comment 4 Sławomir Nizio 2020-02-22 21:06:30 UTC]

(In reply to Jonas Stein from comment #2)
> Thank you for the report. Please recompile and 
> *attach* the logfiles and 
> paste the emerge info as described on
> https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket
> We need to have all information at hand before ticket assignment, so that
> the maintainer can look after it in one session with minimal number of
> callbacks.
> Please reopen this ticket (Status:unconfirmed) afterwards.

I'm building the pkg after the fix; won't waste time on rebuilding also without the fix. Not wanting to sound like ass - it's just… well.

And there's no nice build failure to show, just silently dropped feature, originally reported in https://bugs.sabayon.org/show_bug.cgi?id=5883.

[Comment 5 Sławomir Nizio 2020-02-22 21:13:20 UTC]

Last thing :)

octave with imagemagick 7 doesn't build anyway:



libinterp/corefcn/__magick_read__.cc: In function ‘octave_value_list read_indexed_images(const std::vector<Magick::Image>&, const Array<int>&, const octave_idx_type&, const octave_scalar_map&)’:
libinterp/corefcn/__magick_read__.cc:311:21: error: ‘IndexPacket’ in namespace ‘Magick’ does not name a type
       const Magick::IndexPacket *pix
                     ^~~~~~~~~~~
libinterp/corefcn/__magick_read__.cc:318:50: error: ‘pix’ was not declared in this scope
               img_fvec[idx++] = static_cast<P> (*pix);
                                                  ^~~
libinterp/corefcn/__magick_read__.cc:321:11: error: ‘pix’ was not declared in this scope
           pix -= col_shift;