From: Paul Eggert <eggert@cs.ucla.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Unable to find libgif/libungif on RHEL 6
Date: Thu, 10 Sep 2015 11:36:09 -0700 [thread overview]
Message-ID: <55F1CD99.6010906@cs.ucla.edu> (raw)
In-Reply-To: <CAFyQvY3O_PKmaa_UbWGcdfY_BCGpwfuZZVcCdyOv6Fadz4W3Jw@mail.gmail.com>
Kaushal Modi wrote:
> Something else is not right in my system.. but at least I am glad I can
> still build emacs, be it without gif.
Yes, that's what I do. Your other problems can undoubtedly be fixed by using
the proper combination of environment variables and configure options, though
these days it's typically not worth the trouble.
> Just as we have LIBOTF_CFLAGS, LIBOTF_LIBS,
> can we not have LIBGIF_CFLAGS and LIBGIF_LIBS?
It'd be a pain, as LIBOTF_CFLAGS is generated automatically by configure.ac via
EMACS_CHECK_MODULES via PKG_CHECK_MODULES via pkg-config, but libgif typically
isn't packaged and so we'd have to do a lot of stuff by hand in configure.ac.
This what we did ten or twenty years ago but nowadays it's typically not worth
the trouble. Builders who care about this and are expert enough can set env
vars and configure options accordingly, which is about the best that can be
expected for this messy area.
next prev parent reply other threads:[~2015-09-10 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 4:58 Unable to find libgif/libungif on RHEL 6 Kaushal Modi
2015-09-10 5:14 ` Kaushal Modi
2015-09-10 10:06 ` Paul Eggert
2015-09-10 12:15 ` Kaushal Modi
2015-09-10 14:30 ` Paul Eggert
2015-09-10 15:16 ` Stefan Monnier
2015-09-10 15:27 ` Kaushal Modi
2015-09-10 18:36 ` Paul Eggert [this message]
2015-09-10 21:11 ` Wolfgang Jenkner
2015-09-11 2:51 ` Kaushal Modi
2015-09-11 12:23 ` Wolfgang Jenkner
2015-09-11 14:04 ` 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=55F1CD99.6010906@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).