From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: George myglc2 Clemmer <myglc2@gmail.com>, 31367@debbugs.gnu.org
Subject: bug#31367: ERROR: In procedure scm-error: no code for module (guix build utils)
Date: Fri, 25 May 2018 14:22:29 +0200 [thread overview]
Message-ID: <87o9h3hqm2.fsf@gnu.org> (raw)
In-Reply-To: <87k1rs3vcm.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Roel Janssen <roel@gnu.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> George myglc2 Clemmer <myglc2@gmail.com> skribis:
>>>
>>>> cd guix && guix environment guix -- make
>>>> The following derivations will be built:
>>>> /gnu/store/mcfys0glgv1hnq5mrcs9xnmn4bpzr3ys-profile.drv
>>>> /gnu/store/qikmbskc6598vld2lhb2pn30h1rwxgc8-xdg-mime-database.drv
>>>> /gnu/store/izxixb30i4r79gahirb4nj5ay0z8nzv1-info-dir.drv
>>>> /gnu/store/bdg4x3925r9l3458li48hp1i26shd7yw-manual-database.drv
>>>> Backtrace:
>>>> 10 (primitive-load "/gnu/store/611mdvnasj59v5j46g8mhq7aw0g?")
>>>> In ice-9/eval.scm:
>>>> 721:20 9 (primitive-eval (begin (use-modules (guix build #) ?) ?))
>>>> In ice-9/psyntax.scm:
>>>> 1235:36 8 (expand-top-sequence ((begin (use-modules (# # ?) ?) ?)) ?)
>>>> 1182:24 7 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
>>>> 1182:24 6 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
>>>> 285:10 5 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
>>>> In ice-9/boot-9.scm:
>>>> 3365:20 4 (process-use-modules _)
>>>> 222:17 3 (map1 (((guix build utils)) ((srfi srfi-1)) ((srfi ?)) ?))
>>>> 3366:31 2 (_ ((guix build utils)))
>>>> 2791:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ ?)
>>>> In unknown file:
>>>> 0 (scm-error misc-error #f "~A ~S" ("no code for modu?" ?) ?)
>>>>
>>>> ERROR: In procedure scm-error:
>>>> no code for module (guix build utils)
>>>> Creating manual page database...
>>>> builder for `/gnu/store/izxixb30i4r79gahirb4nj5ay0z8nzv1-info-dir.drv' failed with exit code 1
>>>
>>> I’m merging it with <https://bugs.gnu.org/28144>. No fix yet but we’re
>>> working on it. In the meantime, ‘guix pull’ may allow you to work
>>> around it.
>>
>> I'm using a git checkout of Guix, and I am encountering this bug with
>> version 217af8ae7. Is there a work-around?
>
> In essence you need to recompile guix/profiles.go.
That solved it for me. Thanks!
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2018-05-25 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:17 bug#31367: ERROR: In procedure scm-error: no code for module (guix build utils) George myglc2 Clemmer
2018-05-06 15:22 ` Ludovic Courtès
2018-05-06 18:13 ` George Clemmer
2018-05-25 9:28 ` Roel Janssen
2018-05-25 9:56 ` Ricardo Wurmus
2018-05-25 10:01 ` Roel Janssen
2018-05-25 10:03 ` Ludovic Courtès
2018-05-25 12:22 ` Roel Janssen [this message]
[not found] ` <cucpnu4gaxm.fsf@gmail.com>
2018-12-14 1:32 ` George Clemmer
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=87o9h3hqm2.fsf@gnu.org \
--to=roel@gnu.org \
--cc=31367@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=myglc2@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.
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).