From: joakim@verona.se
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7955@debbugs.gnu.org
Subject: bug#7955: configure does not thoroughly test for ImageMagick includes
Date: Wed, 02 Feb 2011 10:30:44 +0100 [thread overview]
Message-ID: <m3lj1y941n.fsf@verona.se> (raw)
In-Reply-To: <87bp2vb18c.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 01 Feb 2011 21:48:35 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> Joakim, mind taking a look at this? Thanks.
I'll ask the ImageMagick maintainers.
If that fails, I can try to add a specific configure check for the include file
we need.
If I could get a pointer to a virtualization image for rhel 4.8 that
would be splendid too.
>
> Glenn Morris <rgm@gnu.org> writes:
>
>> Package: emacs
>> Version: 24.0.50
>> Severity: minor
>>
>> I tried to build the current trunk on a RHEL 4.8 system.
>> This has ImageMagick 6.0.7 installed.
>> configure decided that ImageMagick was usable:
>>
>> checking for Wand... yes
>> checking IMAGEMAGICK_CFLAGS...
>> checking IMAGEMAGICK_LIBS... -lWand -lMagick
>> checking for MagickExportImagePixels... no
>> [...]
>> Does Emacs use imagemagick? yes
>>
>> However, the build failed because of this:
>>
>> image.c:7455:29: warning: wand/MagickWand.h: No such file or directory
>>
>> The system has /usr/include/wand/magick_wand.h, but it does not
>> have /usr/include/wand/MagickWand.h. Looks like the former is now
>> deprecated. The latter does exist on RHEL 5.5, with ImageMagick 6.2.8.
>>
>> Obviously I can just re-configure using --without-imagemagick, but
>> Emacs should do this for me. Either configure should test for some
>> required minimum version of ImageMagick (I was not able to find out in
>> what version wand/MagickWand.h was added); or image.c should fall back
>> to wand/magick_wand.h if it can.
--
Joakim Verona
next prev parent reply other threads:[~2011-02-02 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 20:38 bug#7955: configure does not thoroughly test for ImageMagick includes Glenn Morris
2011-02-02 2:48 ` Chong Yidong
2011-02-02 9:30 ` joakim [this message]
2011-02-02 19:32 ` Glenn Morris
2011-02-03 8:16 ` bug#7955: reply from the IM team joakim
2011-02-08 19:19 ` Glenn Morris
2011-02-11 23:38 ` bug#7955: patch for imagemagick header rename joakim
2011-02-12 1:11 ` Glenn Morris
2011-02-12 22:39 ` Chong Yidong
2011-02-13 0:28 ` joakim
2011-02-12 23:37 ` Glenn Morris
2011-02-14 20:13 ` Glenn Morris
2011-02-14 20:37 ` joakim
2011-02-15 2:51 ` Glenn Morris
2011-04-07 21:00 ` Glenn Morris
2011-04-12 3:56 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lj1y941n.fsf@verona.se \
--to=joakim@verona.se \
--cc=7955@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).