From: Neil Jerram <neil@ossau.homelinux.net>
To: mhw@netris.org
Cc: guile-user@gnu.org, Federico Beffa <beffa@ieee.org>
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Mon, 15 Sep 2014 10:49:49 +0100 [thread overview]
Message-ID: <22d07a740caf3be621c11d4d7dbd1094@ossau.homelinux.net> (raw)
In-Reply-To: <87ha09y96w.fsf@netris.org>
On 2014-09-15 02:16, mhw@netris.org wrote:
> Federico Beffa <beffa@ieee.org> writes:
>
>> Neil Jerram <neil@ossau.homelinux.net> writes:
>>
>>>
>>> This is just a guess, but what happens if you do this:
>>>
>>> $ LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/guile
>>>
>>> Regards,
>>> Neil
>>
>> With this it works!
>>
>> I notice that there is an /etc/ld.so.cache file. Do I somehow need to
>> update
>> it?
>
> Yes, you update it by running "ldconfig" as root. This needs to be
> done
> when installing libraries outside of your package manager, not only for
> Guile, but for essentially all packages containing libraries.
I agree that this will allow /usr/local/bin/guile to load
/usr/local/lib/libguile*.
However, won't it also cause /usr/bin/guile (2.0.5) to load
/usr/local/lib/libguile* (2.0.11) ? If not, what is the mechanism that
tells /usr/bin/guile (2.0.5) to load /usr/lib/libguile* (2.0.5) instead
of /usr/local/lib/libguile* (2.0.11) ?
Thanks,
Neil
next prev parent reply other threads:[~2014-09-15 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 15:37 guile-2.0.11 installation on system with 2.0.5 Federico Beffa
2014-09-15 1:16 ` mhw
2014-09-15 9:49 ` Neil Jerram [this message]
2014-09-15 10:22 ` Federico Beffa
2014-09-15 10:44 ` Chris Vine
2014-09-15 14:15 ` Mark H Weaver
2014-09-15 10:27 ` Chris Vine
-- strict thread matches above, loose matches on Subject: below --
2014-09-16 11:09 Federico Beffa
2014-09-16 13:13 ` Federico Beffa
2014-09-16 18:16 ` David Pirotte
2014-09-15 16:46 Federico Beffa
2014-09-15 17:33 ` David Pirotte
2014-09-15 11:46 Federico Beffa
2014-09-15 15:00 ` Chris Vine
2014-09-16 16:26 ` Mark H Weaver
2014-09-14 15:42 Federico Beffa
2014-09-14 23:07 ` Chris Vine
2014-09-15 7:50 ` Ludovic Courtès
2014-09-14 8:02 Federico Beffa
2014-09-13 12:52 Federico Beffa
2014-09-14 1:17 ` Vernon Oberholzer
2014-09-14 14:32 ` Neil Jerram
2014-09-14 14:33 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22d07a740caf3be621c11d4d7dbd1094@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=beffa@ieee.org \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).