unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Mon, 15 Sep 2014 11:44:01 +0100	[thread overview]
Message-ID: <20140915114401.763d1916@bother.homenet> (raw)
In-Reply-To: <CAKrPhPM-CiiamxbwW1zT1RZqBBx237fpFcDqv75ZOPC+Ywu6KQ@mail.gmail.com>

On Mon, 15 Sep 2014 12:22:27 +0200
Federico Beffa <beffa@ieee.org> wrote:
> On Mon, Sep 15, 2014 at 11:49 AM, Neil Jerram
[snip]
> > 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
> >
> 
> yes, that's what I've found out by running ldconfig. Both versions now
> show version 2.0.11 in the startup message.

I would strongly advise you not to have two binary compatible versions
of any given library on your system at the same time, unless you really
know what you are doing.  Otherwise you are at the mercy of the look-up
order of the dynamic linker.  It is much better simply to upgrade your
system to guile-2.0.11 using your distribution's package manager. Since
guile maintains binary compatibility between micro versions, you should
be absolutely fine (and you can always back out if not).

However if you insist on doing what you are doing, see my separate
posting and use environmental variables to achieve what you want.

Chris



  reply	other threads:[~2014-09-15 10:44 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
2014-09-15 10:22     ` Federico Beffa
2014-09-15 10:44       ` Chris Vine [this message]
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=20140915114401.763d1916@bother.homenet \
    --to=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).