From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: elf@ee.ryerson.ca, emacs-devel@gnu.org
Subject: Re: emacs dumps core using gnus
Date: Mon, 11 Feb 2002 21:57:12 +0200 [thread overview]
Message-ID: <1858-Mon11Feb2002215711+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200202111848.g1BIm7Z06906@aztec.santafe.edu> (message from Richard Stallman on Mon, 11 Feb 2002 11:48:07 -0700 (MST))
> Date: Mon, 11 Feb 2002 11:48:07 -0700 (MST)
> From: Richard Stallman <rms@gnu.org>
>
> Unfortunately, this doesn't seem to work with libungif. The header it
> installes, gif_lib.h, has only this:
>
> #define GIF_LIB_VERSION " Version 4.0, "
>
> which doesn't reveal the minor version number, which is what we need
> here.
>
> Can it be done by seeing which files are present in the directories
> that would be searched?
Sorry, I'm not following: what files did you have in mind? If those
are the sources of libungif, then we cannot be sure the sources are
available when Emacs is built: they could have just the header and
libungif.so.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-11 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x0pu3iex5q.fsf@www.ee.ryerson.ca>
[not found] ` <Pine.SUN.3.91.1020206130807.3481A-100000@is>
[not found] ` <15457.20348.248746.712978@gargle.gargle.HOWL>
2002-02-08 13:55 ` emacs dumps core using gnus Richard Stallman
2002-02-10 1:29 ` luis fernandes
2002-02-10 11:28 ` Eli Zaretskii
2002-02-11 18:48 ` Richard Stallman
2002-02-11 19:57 ` Eli Zaretskii [this message]
2002-02-13 15:37 ` Richard Stallman
2002-02-14 11:10 ` Eli Zaretskii
2002-02-15 10:37 ` Richard Stallman
2002-02-15 15:58 ` luis fernandes
2002-02-15 18:50 ` Eli Zaretskii
2002-02-16 9:35 ` Pavel Janík
2002-02-16 21:56 ` Richard Stallman
2002-02-16 21:56 ` Richard Stallman
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=1858-Mon11Feb2002215711+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=elf@ee.ryerson.ca \
--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).