unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: chris@cvine.freeserve.co.uk, guile-user@gnu.org
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Mon, 15 Sep 2014 13:46:07 +0200	[thread overview]
Message-ID: <CAKrPhPO-p4rbV+Vzw+MRYSGhrJyy7vKa7za_yOHiO8r0TdTNVA@mail.gmail.com> (raw)

Chris Vine <chris@cvine.freeserve.co.uk> writes:

> On Sun, 14 Sep 2014 21:16:39 -0400
> 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 would not recommend doing that where the OP has two _binary
> compatible_ versions of the same library in different prefixes (as he
> appears to have), otherwise the one which will be found and linked in
> will depend on the dynamic linker's look-up order from
> reading /etc/ld.so.conf.  This could be the old micro version where in
> a given case the OP in fact wants the new one, or conversely the new
> micro version where he in fact wants the old one.
>
> Presumably in the general case he wants the micro version supplied by
> the distribution's package manager to be linked in, otherwise he would
> simply have replaced that one with the (binary compatible) newer
> version of the same library.  Presumably also he wants the updated
> version which he has installed to be linked in instead only when
> specially called.  If that is right, he is much better off putting his
> updated version in a directory which is _not_ specified
> in /etc/ld.so.conf, and invoking it on the occasions when he does not
> want the general case to apply by setting the LD_LIBRARY_PATH
> environmental variable for that invocation.  Then he is guaranteed to
> have the correct version loaded in.
>
> Chris

Your guess is correct: The distribution that I'm using (Debian wheezy)
ships 2.0.5 as the newest guile version and I need to keep it to satisfy
dependencies of other distribution supplied packages.  However, I would
like to experiment with a newer version of guile. I will then follow
your advice and install it in a different directory.

Thanks for all the explanations!
Regards,
Fede



             reply	other threads:[~2014-09-15 11:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 11:46 Federico Beffa [this message]
2014-09-15 15:00 ` guile-2.0.11 installation on system with 2.0.5 Chris Vine
2014-09-16 16:26   ` Mark H Weaver
  -- 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-14 15:42 Federico Beffa
2014-09-14 23:07 ` Chris Vine
2014-09-15  7:50 ` Ludovic Courtès
2014-09-14 15:37 Federico Beffa
2014-09-15  1:16 ` mhw
2014-09-15  9:49   ` Neil Jerram
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
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=CAKrPhPO-p4rbV+Vzw+MRYSGhrJyy7vKa7za_yOHiO8r0TdTNVA@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=chris@cvine.freeserve.co.uk \
    --cc=guile-user@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).