unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ethan J <doubleplusgood23@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix offloading fails to register GC root
Date: Mon, 20 Jun 2016 09:15:36 +0200	[thread overview]
Message-ID: <87r3bs8h5z.fsf@gnu.org> (raw)
In-Reply-To: <CAJhL_KQngSvjy64hEx=Cd3A2=poX5YRL4SgDsP2iKt6LXpRXEA@mail.gmail.com> (Ethan J.'s message of "Mon, 20 Jun 2016 02:22:46 +0000")

Hi,

Ethan J <doubleplusgood23@gmail.com> skribis:

> I was trying to use the guix offloading capability to offloading building
> of packages from my laptop to a more power server. After fighting with lsh
> to get ssh working [1], I ran into this error while running guix build -i
> hello http://paste.lisp.org/display/318673

This:

--8<---------------cut here---------------start------------->8---
ERROR: In procedure scm-error:
ERROR: no code for module (guix config)
--8<---------------cut here---------------end--------------->8---

… indicates that the Guix modules are not in ‘GUILE_LOAD_PATH’ on the
build machine.  The manual hints at it, though I admit it leaves sorting
out the details as an exercise to the user (see
<https://www.gnu.org/software/guix/manual/html_node/Daemon-Offload-Setup.html>):

     The ‘guix’ command must be in the search path on the build machines,
  since offloading works by invoking the ‘guix archive’ and ‘guix build’
  commands.  In addition, the Guix modules must be in ‘$GUILE_LOAD_PATH’
  on the build machine—you can check whether this is the case by running:

       lsh build-machine guile -c "'(use-modules (guix config))'"

Could you check ~/.bash_profile or ~/.profile on the target machine and
make sure that it sets ‘GUILE_LOAD_PATH’ and ‘GUILE_LOAD_COMPILED_PATH’
appropriately?

HTH,
Ludo’.

  reply	other threads:[~2016-06-20  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20  2:22 guix offloading fails to register GC root Ethan J
2016-06-20  7:15 ` Ludovic Courtès [this message]
2016-06-20 21:01   ` Ethan J
2016-06-21  2:52     ` Ethan J

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=87r3bs8h5z.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=doubleplusgood23@gmail.com \
    --cc=help-guix@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).