From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: configure tests for graphics libraries
Date: Mon, 25 Feb 2002 08:13:31 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1020225081133.5689E-100000@is> (raw)
In-Reply-To: <200202241758.g1OHw1n15025@aztec.santafe.edu>
On Sun, 24 Feb 2002, Richard Stallman wrote:
> I just saw a suggestion that the existence of the function
> EGifPutExtensionLast will distinguish the newer version of libungif
> from the problematic one, but I can't currently check that.
>
> Can anyone else verify that?
Verified; it's true. Version 4.1.0 doesn't have this function, while
v4.1.0b1 does.
So we now have a reliable way of detecting the buggy ungif library, we
just need to ask the maintainers to never remove that function from the
library ;-)
Thanks, Dave.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-25 6:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqr8nojomi.fsf@djlvig.dl.ac.uk>
[not found] ` <200202162157.g1GLvIG10113@aztec.santafe.edu>
[not found] ` <rzqpu30xfuu.fsf@djlvig.dl.ac.uk>
[not found] ` <200202220431.g1M4VbB13843@aztec.santafe.edu>
[not found] ` <rzq664omhgf.fsf@djlvig.dl.ac.uk>
2002-02-24 17:58 ` configure tests for graphics libraries Richard Stallman
2002-02-25 6:13 ` Eli Zaretskii [this message]
2002-02-26 20:15 ` Richard Stallman
2002-02-27 10:19 ` Eli Zaretskii
2002-02-28 21:24 ` Dave Love
2002-03-01 21:24 ` Richard Stallman
2002-03-01 23:24 ` Pavel Janík
2002-03-03 14:38 ` Richard Stallman
2002-03-06 19:52 ` Dave Love
2002-03-08 9:09 ` Richard Stallman
2002-03-17 18:27 ` Dave Love
2002-03-18 20:07 ` Richard Stallman
2002-03-18 20:07 ` Richard Stallman
2002-03-19 6:25 ` Eli Zaretskii
2002-03-28 23:52 ` Dave Love
2002-03-28 23:43 ` Dave Love
2002-03-30 3:44 ` Richard Stallman
2002-03-30 8:38 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.91.1020225081133.5689E-100000@is \
--to=eliz@is.elta.co.il \
--cc=d.love@dl.ac.uk \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.