From: Marius Bakke <mbakke@fastmail.com>
To: Timothy Sample <samplet@ngyro.com>, 36723@debbugs.gnu.org
Subject: bug#36723: [core-updates] Error building module-import-compiled
Date: Thu, 18 Jul 2019 21:38:29 +0200 [thread overview]
Message-ID: <877e8f5e16.fsf@devup.no> (raw)
In-Reply-To: <87k1cf5ilr.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 2435 bytes --]
Timothy Sample <samplet@ngyro.com> writes:
> Hi,
>
> Whenever I try to build the following (i.e., using “guix build -f”)
>
> (use-modules (guix gexp)
> (guix modules))
>
> (scheme-file
> "test.scm"
> (with-imported-modules (source-module-closure
> '((gnu build file-systems)))
> #~(values #t)))
>
> it says:
>
> -----
> building /gnu/store/2gmxyxpfs0a2j6pcn9xagam6hczlvihb-module-import-compiled.drv...
> [ 1/14] Loading './gnu/build/file-systems.scm'...
> [ 2/14] Loading './gnu/system/file-systems.scm'...
> [ 3/14] Loading './gnu/system/uuid.scm'...
> [ 4/14] Loading './guix/build/bournish.scm'...
> [ 5/14] Loading './guix/build/syscalls.scm'...
> Backtrace:
> 11 (primitive-load "/gnu/store/qz6d59zqvdd5pj9hprk7sfjkpy3?")
> In ice-9/eval.scm:
> 619:8 10 (_ #f)
> In srfi/srfi-1.scm:
> 466:18 9 (fold #<procedure 7ffff5d2d520 at ice-9/eval.scm:336:1?> ?)
> 466:18 8 (fold #<procedure 7ffff54bc2c0 at ice-9/eval.scm:336:1?> ?)
> 466:18 7 (fold #<procedure 7ffff54c3dc0 at ice-9/eval.scm:336:1?> ?)
> In ice-9/eval.scm:
> 619:8 6 (_ #(#(#<directory (guix build utils) 7ffff6f53500>) # ?))
> In ice-9/boot-9.scm:
> 2312:4 5 (save-module-excursion _)
> In unknown file:
> 4 (primitive-load "./guix/build/syscalls.scm")
> In ice-9/eval.scm:
> 619:8 3 (_ #f)
> In ice-9/boot-9.scm:
> 2071:24 2 (call-with-deferred-observers #<procedure 7ffff50e4700 ?>)
> 260:13 1 (for-each #<procedure 7ffff50e4480 at ice-9/boot-9.scm?> ?)
> In unknown file:
> 0 (scm-error misc-error #f "~A ~S" ("re-exporting loc?" ?) ?)
>
> ERROR: In procedure scm-error:
> re-exporting local variable: AT_SYMLINK_NOFOLLOW
> builder for `/gnu/store/2gmxyxpfs0a2j6pcn9xagam6hczlvihb-module-import-compiled.drv' failed with exit code 1
> -----
>
> Importing “(guix build syscalls)” by itself using
> “with-imported-modules” works fine.
>
> This is needed when building the Shepherd service for mounting file
> systems, so it prevents me from building any systems on core-updates
> (for example, building a VM or reconfiguring). I did try (just to be
> sure) running “make clean-go” and then recompiling, but it didn’t help.
Reverting 456c7ade095cce96f47389c37a4fe3b0390047fd makes the problem
disappear.
I don't really understand why, though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-07-18 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 17:59 bug#36723: [core-updates] Error building module-import-compiled Timothy Sample
2019-07-18 19:38 ` Marius Bakke [this message]
2019-07-18 22:55 ` Ludovic Courtès
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=877e8f5e16.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=36723@debbugs.gnu.org \
--cc=samplet@ngyro.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).