From: Alexis <flexibeast@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Building emacs errors: libraries present
Date: Sun, 08 Feb 2015 01:02:16 +1100 [thread overview]
Message-ID: <87siehq0pj.fsf@gmail.com> (raw)
In-Reply-To: <87siehrgqg.fsf@gmail.com>
Tory S. Anderson writes:
> Okay; I've succeeded finally in building by soft-linking all the
> libraries it SHOULD have been finding into the main
> directories. I'm not sure why it cannot use libpng 16 and
> instead requires 15. E.g. I did this:
>
> sudo ln -s /anaconda/lib/libpng15.so /usr/lib64/
>
> Taking care of any non-found files that way solved all
> problems.
>
> ldconfig looks interesting, but I don't seem to have a manpage
> on it. Unfortunately, it didn't solve the issue. Soft links
> seemed to do the trick for me.
Very odd that your system doesn't have a manpage for ldconfig(8)!
Here's the opening paragraph of that man page on my system:
"ldconfig creates, updates, and removes the necessary links and
cache (for use by the run-time linker, ld.so) to the most recent
shared libraries found in the directories specified on the command
line, in the file /etc/ld.so.conf, and in the trusted directories
(/usr/lib and /lib). ldconfig checks the header and file names of
the libraries it encounters when determining which versions should
have their links updated. ldconfig ignores symbolic links when
scanning for libraries."
Basically, when you install new shared libraries on your system,
you need to run /sbin/ldconfig in order to refresh the cache of
available shared libraries. As someone else has pointed out, the
directories searched for libraries is specified in /etc/ld.so.conf
and related files; if you install shared libraries outside of
those paths, you'll need to add the new paths to /etc/ld.so.conf
(or possibly some other file, depending on the system's setup).
How are you installing the extra libraries? Are you installing the
relevant -devel packages from your distro's repos, or are you
manually compiling and installing them yourself? If the latter,
then you'll need, as noted elsewhere in this thread, to make sure
they're being installed in a path specified by /etc/ld.so.conf, or
modify the latter file appropriately.
Needing to create symbolic links manually, as you have done,
should normally not be necessary.
Alexis.
next prev parent reply other threads:[~2015-02-07 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 3:27 Building emacs errors: libraries present Tory S. Anderson
2015-02-06 7:50 ` Eli Zaretskii
2015-02-06 12:47 ` Tory S. Anderson
2015-02-06 12:54 ` Alexis
2015-02-07 13:30 ` Tory S. Anderson
2015-02-07 14:02 ` Alexis [this message]
2015-02-06 18:25 ` Dale Snell
[not found] ` <mailman.19390.1423226883.1147.help-gnu-emacs@gnu.org>
2015-02-07 10:09 ` Anssi Saari
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=87siehq0pj.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=help-gnu-emacs@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.
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).