From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: configure tests for graphics libraries
Date: Sun, 24 Feb 2002 10:58:01 -0700 (MST) [thread overview]
Message-ID: <200202241758.g1OHw1n15025@aztec.santafe.edu> (raw)
In-Reply-To: <rzq664omhgf.fsf@djlvig.dl.ac.uk> (message from Dave Love on 23 Feb 2002 13:54:40 +0000)
Yes. One change checks for the necessary version of the jpeg library.
The other defaults to not using libungif and tells you if it's found a
copy that may be dangerous and that you have to enable it explicitly,
knowing you have a suitable version. (I guess that's subject to
problems if you run the binary on a system with a different shared
library, but that's too bad.)
I see. That sounds like maybe the right thing--people are talking
about doing just that. I think none of us realized that your patch
did this. Perhaps everyone else misunderstood the description just as
I did.
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?
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next parent reply other threads:[~2002-02-24 17:58 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 ` Richard Stallman [this message]
2002-02-25 6:13 ` configure tests for graphics libraries Eli Zaretskii
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
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=200202241758.g1OHw1n15025@aztec.santafe.edu \
--to=rms@gnu.org \
--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 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).