Yup everything seems to works, sans the random 404 errors.

Thanks again,
Ethan

On Mon, Jun 20, 2016 at 5:01 PM Ethan J <[email protected]> wrote:

> Ah, I see. I'll fix that then.
>
> Thanks,
> Ethan.
>
> On Mon, Jun 20, 2016 at 3:15 AM Ludovic Courtès <[email protected]> wrote:
>
>> Hi,
>>
>> Ethan J <[email protected]> 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 via email to