From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: (Geiser or guile bug) Guix-daemon output is missing
Date: Sun, 06 Sep 2015 23:28:43 +0200 [thread overview]
Message-ID: <87lhcj44qc.fsf@gnu.org> (raw)
In-Reply-To: <87d1xvx6lb.fsf@gmail.com> (Alex Kost's message of "Sun, 06 Sep 2015 12:03:28 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Now the bug itself:
>
> 1. Start Geiser (M-x run-guile)
>
> 2. Make a scheme buffer and evaluate (use-modules (guix scripts build))
> there using "C-x C-e" or "C-M-x" (or any other "geiser-eval-…"
> command). This is important: do not ,use module in the REPL;
> evaluate ‘use-modules’ clause in a scheme buffer!
>
> 3. Go to the REPL and run the following there:
>
> (catch 'quit (lambda () (guix-build "test-package")) (const #t)).
>
> You get only "The following derivation will be built: …" but there is no
> build output from guix-daemon.
Ha ha! Try this before:
(current-build-output-port (current-error-port))
The trick here is that ‘current-build-output-port’ is initialized to
(current-error-port), but that initialization happens at the top-level,
apparently before Geiser has rebound ‘current-error-port’, hence the
silence.
HTH!
Ludo’.
next prev parent reply other threads:[~2015-09-06 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 9:03 (Geiser or guile bug) Guix-daemon output is missing Alex Kost
2015-09-06 21:28 ` Ludovic Courtès [this message]
2015-09-07 19:58 ` Alex Kost
2015-09-09 16:47 ` Alex Kost
2015-09-09 20:11 ` Ludovic Courtès
2015-09-09 21:24 ` Alex Kost
2015-09-10 16:44 ` Alex Kost
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=87lhcj44qc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@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.
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).