Re: guile-2.0.11 installation on system with 2.0.5

[Chris Vine <chris@cvine.freeserve.co.uk>]

On Sun, 14 Sep 2014 17:42:58 +0200
Federico Beffa <beffa@ieee.org> wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
> 
> > It may be that, while /usr/local/bin/guile is indeed from the new
> > version, it ends up loading .scm and .go files from the old version.
> >
> > You could check that by running:
> >
> >   strace -o log /usr/local/bin/guile --version
> >
> > and grepping for .scm and .go files in ‘log’.
> >
> > That could happen, for instance, if there’s a GUILE_LOAD_PATH or
> > GUILE_LOAD_COMPILED_PATH environment variable pointing to
> > /usr/share/guile/...
> >
> 
> Yes, that's what happens. I can see libraries from /usr/share and
> /usr/lib/guile being used.
> 
> I do not have any GUILE_LOAD_* environment variable defined. However,
> I see in the "log" file generated as suggested that
> the /etc/ld.so.cache file gets opened. Should I need somehow to
> update it?

If it is any use to you, to run guile-1.8 on a guile-2.0 system (which
I rarely do) I set the following environmental variables in the script
which starts guile and/or which compiles or loads anything which uses
the 1.8 version of libguile.

  export LD_LIBRARY_PATH=/opt/guile18/lib
  export PATH=/opt/guile18/bin:$PATH
  export GUILE_LOAD_PATH=/opt/guile18/share/guile/1.8:/opt/guile18/share/guile/site:/opt/guile18/share/guile
  export PKG_CONFIG_PATH=/opt/guile18/lib/pkgconfig:$PKG_CONFIG_PATH
  export LDFLAGS=-L/opt/guile18/lib:$LDFLAGS

For guile-2.0 you will probably also want to set GUILE_LOAD_COMPILED_PATH.

However, generally this is not a very sensible approach if you are upgrading
the same minor version of guile.  It would be better to build guile-2.0.11
using the debian build scripts and replace guile-2.0.5 entirely.

Chris