unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs master build failing on RHEL 6.8 [image.c]
Date: Tue, 4 Jun 2019 12:17:26 -0700	[thread overview]
Message-ID: <dfb8e173-3097-bd4c-a681-f932371d9b8d@cs.ucla.edu> (raw)
In-Reply-To: <CAFyQvY3Ka1SCRyO+-ZroFaBmkOgMyoWqjFnPXJfzjd-HSZuoYw@mail.gmail.com>

On 6/4/19 4:49 AM, Kaushal Modi wrote:
> /usr/bin/ld: warning: libgmp.so.3, needed by
> /cad/adi/apps/gnu/linux/x86_64/6/lib/libhogweed.so.2, may conflict with
> libgmp.so.10

This looks like some other glitch in your build process, something you 
should fix but unrelated to the GifErrorString problem.

> image.o: In function `gif_load':
> image.c:(.text+0xa76b): undefined reference to `GifErrorString'
> image.c:(.text+0xa7d8): undefined reference to `GifErrorString'
> image.c:(.text+0xaefe): undefined reference to `GifErrorString'
> collect2: error: ld returned 1 exit status

It looks like your GIFLIB implementation does not match its .h files. 
image.c calls GifErrorString only if HAVE_GIFERRORSTRING, which is true 
only if (5 < GIFLIB_MAJOR + (1 <= GIFLIB_MINOR)). So my guess is that 
your GIFLIB .h files are claiming to be release 5.1 or later, but the 
implementation predates 5.1. Please look into that. The situation is 
somewhat tricky as some GIFLIB .h files apparently define incorrect 
values for GIFLIB_MINOR.

I don't see any recent changes to image.c that would explain your problem.




  reply	other threads:[~2019-06-04 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 11:49 Emacs master build failing on RHEL 6.8 [image.c] Kaushal Modi
2019-06-04 19:17 ` Paul Eggert [this message]
2019-06-04 19:36   ` Kaushal Modi
2019-06-08 14:24     ` Richard Kim
2022-01-16 18:09       ` Eli Zaretskii
2019-06-10  2:01     ` Kaushal Modi

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=dfb8e173-3097-bd4c-a681-f932371d9b8d@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    /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).