From: Frank Schmitt <ich@frank-schmitt.net>
Cc: emacs-devel@gnu.org
Subject: Re: [ich@frank-schmitt.net: Build failure under Suse 10.0]
Date: Mon, 06 Nov 2006 10:51:33 +0100 [thread overview]
Message-ID: <m3u01cj42i.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <454EFE1C.4070907@swipnet.se> (Jan Djärv's message of "Mon, 06 Nov 2006 10:19:24 +0100")
Jan Djärv <jan.h.d@swipnet.se> writes:
> You have in /usr/local/include/gif_lib.h:
>
> typedef struct {
> int ByteCount;
> char *Bytes;
> } ExtensionBlock;
>
> i.e. no Function member. It may be a stray file from some older
> version. Please make sure it is the correct header file, in your
> previous post you said /usr/include/gif_lib.h had a Function member.
Indeed, that's the problem. I have searched via locate for gif_lib.h but
it didn't return this file as /usr/local is a remote NFS share which
isn't indexed.
The file /usr/local/include/gif_lib.h is a relict from an ancient libgif
(3.0), /usr/include/gif_lib.h is the correct one so the error is a
problem on my side and the bug can be considered closed.
Perhaps it's possible to enhance the configure test for libgif to check
if the installed libgif fulfills emacs requirements.
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
next prev parent reply other threads:[~2006-11-06 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 5:02 [ich@frank-schmitt.net: Build failure under Suse 10.0] Richard Stallman
2006-11-06 7:53 ` Jan Djärv
2006-11-06 8:04 ` Jan Djärv
2006-11-06 8:40 ` Frank Schmitt
2006-11-06 9:19 ` Jan Djärv
2006-11-06 9:51 ` Frank Schmitt [this message]
2006-11-06 10:49 ` Jan Djärv
2006-11-06 21:00 ` Richard Stallman
2006-11-06 22:28 ` Reiner Steib
2006-11-06 22:49 ` Andreas Schwab
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=m3u01cj42i.fsf@mid.gehheimdienst.de \
--to=ich@frank-schmitt.net \
--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.