[Pkg-gmagick-im-team] Bug#764899: libmagickcore-6.q16-dev: Magick-config is missing

[Michael Franzl]

On Thu, 16 Oct 2014 15:46:28 +0200 Vincent Fourmond 
<fourmond at debian.org> wrote:
>   This is indeed a pain. We moved away from Magick-config now that
> ImageMagick is pkg-config ready. Maybe we can still provide
> Magick-config, but not in a standard place (such as
> /usr/lib/ImageMagick or something), so that only very minor
> modifications to RMagick would be necessary ? I'm unsure we want to
> put it back.

Any changes to the old/historical locations would have to be reported to 
the maintainers of the rmagick Ruby Gem (see rubygems.org). In their 
extconf.rb script, they do detection of the various operating systems 
and respective locations of headers etc. Without the rmagick gem 
supporting the new Debian Jessie locations, compilation of the native 
Ruby extension during `gem install rmagick` will always fail.

This is a bit frustrating because this issue makes Jessie unusable for 
development of many Ruby applications.

In any event, I've found out that the package 
graphicsmagick-libmagick-dev-compat actually just creates symlinks. One 
of them is a symlink from

Magick-config -> GraphicsMagick-config

So, I created this symlink manually, and then ran `gem install rmagick` 
again. Magick-config is now found, but the problems don't stop there. 
The next issue is that "wand/MagickWand.h" cannot be found. Inspecting 
extconf.rb of the rmagick gem and having the interactive Ruby Console 
irb, I could find the issue. `have_header` returns `false`:

     irb(main):001:0> require 'mkmf'
     => true
     irb(main):002:0> have_header "wand/MagickWand.h"
     checking for wand/MagickWand.h... no
     => false

I don't have enough expertise in Ruby's mkmf to find out why this is. 
There is a MagickWand.h in /usr/include/ImageMagick-6/wand/

Maybe input can be gotten from the Debian Ruby team?

Thanks,
Michael