From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia@riseup.net>
Cc: 33279-done@debbugs.gnu.org
Subject: bug#33279: guile-readline: error: no code for module
Date: Tue, 06 Nov 2018 12:36:36 +0100 [thread overview]
Message-ID: <8736se5tff.fsf@gnu.org> (raw)
In-Reply-To: <6fe72b3b-edb7-efb7-8b4e-f30e7b746fbb@riseup.net> (swedebugia's message of "Mon, 5 Nov 2018 21:14:26 +0100")
Hello,
swedebugia <swedebugia@riseup.net> skribis:
> exporting these variables did not help:
>
> $ export GUILE_LOAD_PATH=~/.guix-profile/lib/guile/2.2/:$GUILE_LOAD_PATH
> $ export
> GUILE_LOAD_COMPILED_PATH=~/.guix-profile/lib/guile/2.2/:$GUILE_LOAD_COMPILED_PATH
Rather you need:
export GUILE_LOAD_PATH=~/.guix-profile/share/guile/site/2.2:$GUILE_LOAD_PATH
export GUILE_LOAD_COMPILED_PATH=~/.guix-profile/lib/guile/2.2/site-ccache:$GUILE_LOAD_COMPILED_PATH
Better yet, you can install both ‘guile’ and ‘guile-readline’ in the
same profile and you’ll get a message telling you what to do:
--8<---------------cut here---------------start------------->8---
$ guix package -p foo -i guile guile-readline
[...]
La jenaj medi-variablaj difinoj povos esti necesaj:
export PATH="foo/bin${PATH:+:}$PATH"
export GUILE_LOAD_PATH="foo/share/guile/site/2.2${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
export GUILE_LOAD_COMPILED_PATH="foo/lib/guile/2.2/site-ccache:foo/share/guile/site/2.2${GUILE_LOAD_COMPILED_PATH:+:}$GUILE_LOAD_COMPILED_PATH"
--8<---------------cut here---------------end--------------->8---
HTH!
Ludo’.
next prev parent reply other threads:[~2018-11-06 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 20:14 bug#33279: guile-readline: error: no code for module swedebugia
2018-11-06 11:36 ` Ludovic Courtès [this message]
2018-11-06 19:05 ` swedebugia
2018-11-06 20:14 ` Marius Bakke
2018-11-07 16:40 ` bug#33279: GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH on GuixSD Ludovic Courtès
2018-11-07 17:08 ` swedebugia
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736se5tff.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33279-done@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).