From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: [ich@frank-schmitt.net: Build failure under Suse 10.0]
Date: Mon, 06 Nov 2006 11:49:26 +0100 [thread overview]
Message-ID: <454F1336.6070300@swipnet.se> (raw)
In-Reply-To: <m3u01cj42i.fsf@mid.gehheimdienst.de>
Frank Schmitt skrev:
> 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.
>
It already does, search for
checking for EGifPutExtensionLast in -lungif
in the configure output. I suspect this check succeeds because configure
links with your libungif in /usr/lib. Not much we can do if the header file
does not match the lib.
Jan D.
next prev parent reply other threads:[~2006-11-06 10:49 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
2006-11-06 10:49 ` Jan Djärv [this message]
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=454F1336.6070300@swipnet.se \
--to=jan.h.d@swipnet.se \
--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.