From: Wolfgang Jenkner <wjenkner@inode.at>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Unable to find libgif/libungif on RHEL 6
Date: Fri, 11 Sep 2015 14:23:31 +0200 [thread overview]
Message-ID: <85oah9w2sx.fsf@iznogoud.viz> (raw)
In-Reply-To: CAFyQvY2NUSA1kxPx+OE61NF3+rvkgj=PrOdt5xOL08vpYCCKjQ@mail.gmail.com
On Fri, Sep 11 2015, Kaushal Modi wrote:
> The LDFLAGS did the magic, thank you!
Actually,
./configure ... LDFLAGS=-L/path/to/the/lib64 CPPFLAGS=-I/path/to/gifincludedir
should be enough since configure will add -lgif to LIBS anyway (or do
something else to that effect).
> (I wonder why setting the $LD_LIBRARY_PATH and $PKG_CONFIG_PATH env vars
> did not help.)
LD_LIBRARY_PATH is used at runtime by the dynamic linker ld.so(8),
whereas LDFLAGS belongs to the GNU buildsystem, see
(info "(autoconf) Preset Output Variables").
PKG_CONFIG_PATH is a search path for *.pc files, which giflib doesn't
install (as Paul already mentioned), see pkg-config(1).
There are some (completely untested) variations on the theme:
One could pass
LDFLAGS="-L/path/to/the/lib64 -Wl,-rpath=/path/to/the/lib64"
to configure and so avoid changing LD_LIBRARY_PATH.
Or, if you have the static lib64/libgif.a you could link emacs to it
instead (by simply moving away the lib64/libgif.so* you have in your
home directory before building emacs); in this case, you could even
completely remove the giflib stuff from your home directory after
building emacs.
next prev parent reply other threads:[~2015-09-11 12:23 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
2015-09-10 21:11 ` Wolfgang Jenkner
2015-09-11 2:51 ` Kaushal Modi
2015-09-11 12:23 ` Wolfgang Jenkner [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85oah9w2sx.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=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 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.