From: Alex Kost <alezost@gmail.com>
To: guix-devel@gnu.org
Subject: (Geiser or guile bug) Guix-daemon output is missing
Date: Sun, 06 Sep 2015 12:03:28 +0300 [thread overview]
Message-ID: <87d1xvx6lb.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Hello.
There is a strange problem with evaluating a code using Geiser, which
leads to some missing output in a REPL. I have an example demonstrating
the problem using some Guix code, but I would like to have a pure guile
recipe, so that it can be reported.
So how to reproduce the bug. At first, make a file "test-bug.scm"
(attached) and put it somewhere to GUIX_PACKAGE_PATH. Run "guix build
test-package" in shell to make sure that the package is found. The
building will fail, but it's fine for this demonstration. Note that
there is a usual output from guix-daemon ("@ build-started …").
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.
Now if you close the REPL and repeat this recipe but on the 2nd step you
evaluate (use-modules (guix scripts build)) or ,use(guix scripts build)
in the REPL itself, you will see the build output as expected.
So there is something special with this guix-daemon output and with
Geiser synchronous evaluating (using ‘geiser-eval--send/wait’) that
sends this output to a better world.
I appreciate any ideas on solving this bug or making a guix-independent
recipe to reproduce it.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: test-bug.scm --]
[-- Type: text/x-scheme, Size: 305 bytes --]
(define-module (test-bug)
#:use-module (guix packages)
#:use-module (guix build-system trivial)
#:use-module (gnu packages base))
(define-public test-package
(package (inherit hello)
(name "test-package")
(build-system trivial-build-system)
(arguments
'(#:builder (const #t)))))
next reply other threads:[~2015-09-06 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 9:03 Alex Kost [this message]
2015-09-06 21:28 ` (Geiser or guile bug) Guix-daemon output is missing Ludovic Courtès
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=87d1xvx6lb.fsf@gmail.com \
--to=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).