From: ludo@gnu.org (Ludovic Courtès)
To: Fredrik Salomonsson <plattfot@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: build failed: unexpected EOF reading a line
Date: Mon, 11 Sep 2017 09:47:31 +0200 [thread overview]
Message-ID: <87wp55d6cs.fsf@gnu.org> (raw)
In-Reply-To: <CABZcOAS0+P+qgv+aUk6bB-8XLfxgJpT10vGTUT2mpoqGctcQcQ@mail.gmail.com> (Fredrik Salomonsson's message of "Sun, 10 Sep 2017 21:25:21 -0700")
Hi Fredrik,
Fredrik Salomonsson <plattfot@gmail.com> skribis:
> I thought that it might be something wrong with my recipe I was writing. So
> I tested to build the GNU Hello package from the manual (Defining Packages
> <https://www.gnu.org/software/guix/manual/html_node/Defining-Packages.html#Defining-Packages>).
> I copied it into a file called gnu/packages/hello.scm
> After that I ran "guix build -L$(pwd) hello".
> But I'm getting these errors:
>
>> guix: offload: command not found
>> Try `guix --help' for more information.
>> guix build: error: build failed: unexpected EOF reading a line
How did you set up guix-daemon?
Behind the scenes, guix-daemon invokes the internal ‘guix offload’
command. That command requires Guile-SSH¹. In your case, it looks like
Guile-SSH was found at configure-time when building Guix, but is now
missing at run time, hence this “offload: command not found” error.
Could you make sure the GUILE_LOAD_PATH environment variable seen by
guix-daemon points to Guile-SSH?
HTH,
Ludo’.
¹ https://www.gnu.org/software/guix/manual/html_node/Requirements.html
next prev parent reply other threads:[~2017-09-11 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 4:25 build failed: unexpected EOF reading a line Fredrik Salomonsson
2017-09-11 7:47 ` Ludovic Courtès [this message]
[not found] ` <CABZcOARq30BijDzrJRp1Z3izwaN4b2f5Z5ifSTrQ=0D3SByWfQ@mail.gmail.com>
2017-09-12 7:48 ` Ludovic Courtès
2017-09-13 5:19 ` Fredrik Salomonsson
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=87wp55d6cs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=plattfot@gmail.com \
/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).