From: Federico Beffa <beffa@ieee.org>
To: ludo@gnu.org
Cc: guile-user@gnu.org
Subject: Re: guile-2.0.11 installation on system with 2.0.5
Date: Sun, 14 Sep 2014 17:42:58 +0200 [thread overview]
Message-ID: <CAKrPhPMTvjRaSVX5Fy+h=e+vUcrR7=aYVVthLqG8g+zjHDQpcw@mail.gmail.com> (raw)
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?
Thanks,
Fede
next reply other threads:[~2014-09-14 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 15:42 Federico Beffa [this message]
2014-09-14 23:07 ` guile-2.0.11 installation on system with 2.0.5 Chris Vine
2014-09-15 7:50 ` Ludovic Courtès
-- 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: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='CAKrPhPMTvjRaSVX5Fy+h=e+vUcrR7=aYVVthLqG8g+zjHDQpcw@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).