Hi Ludo, Thanks for the help.
On Sat, 03 Dec 2022 at 18:43, Ludovic Courtès <[email protected]> wrote: > Fixed in 9672db290a35f59113682a7f0c17c050a4ae2578. Well, the main issue was that I hit this bug. :-) I tried to see if this trivial example is covered by the test suite but I have not found it. Something like, --8<---------------cut here---------------start------------->8--- (define (something) (with-extensions (list guile-gcrypt) (with-imported-modules (source-module-closure '((guix build utils) (guix profiles))) ;import it (computed-file "empty-tree" #~(begin ;; Put it in scope. (use-modules (guix build utils)) ;; Happily use its 'mkdir-p' procedure. (mkdir-p (string-append #$output "/a/b/c"))))))) ,build (something) --8<---------------cut here---------------end--------------->8--- where ’something’ would be a better name and ’,build’ the real function call. Well, maybe it could help to detect some regression. :-) As people tell: one bug closed, one test added. ;-) Although it requires to talk with the daemon and I do not remember if it is a good idea to add such test. > It’s annoying, but I don’t see how this could be avoided. Well, the error message is not super clear… --8<---------------cut here---------------start------------->8--- building /gnu/store/rh1ii1cjlc0jhkz2aspxcw1mdkr7b2nf-module-import-compiled.drv... 20% [##################### ]builder for `/gnu/store/rh1ii1cjlc0jhkz2aspxcw1mdkr7b2nf-module-import-compiled.drv' failed with exit code 1 build of /gnu/store/rh1ii1cjlc0jhkz2aspxcw1mdkr7b2nf-module-import-compiled.drv failed View build log at '/var/log/guix/drvs/rh/1ii1cjlc0jhkz2aspxcw1mdkr7b2nf-module-import-compiled.drv.gz'. cannot build derivation `/gnu/store/cznhm1wzdv60jwi7fz96cilq925j54i1-empty-tree.drv': 1 dependencies couldn't be built While executing meta-command: ERROR: 1. &store-protocol-error: message: "build of `/gnu/store/cznhm1wzdv60jwi7fz96cilq925j54i1-empty-tree.drv' failed" status: 100 --8<---------------cut here---------------end--------------->8--- …but the log somehow is: --8<---------------cut here---------------start------------->8--- [ 1/56] Loading './guix/base16.scm'... [...] [11/56] Loading './guix/derivations.scm'... ;;; Failed to autoload make-zlib-input-port in (zlib): ;;; no code for module (zlib) ;;; Failed to autoload make-zlib-input-port in (zlib): ;;; no code for module (zlib) ;;; Failed to autoload make-zlib-output-port in (zlib): ;;; no code for module (zlib) ;;; Failed to autoload make-zlib-output-port in (zlib): ;;; no code for module (zlib) Backtrace: [...] 222:17 1 (map1 (((gcrypt hash)) ((guix profiling)) ((rnrs #)) # ?)) 3329:6 0 (resolve-interface (gcrypt hash) #:select _ #:hide _ # _ ?) ice-9/boot-9.scm:3329:6: In procedure resolve-interface: no code for module (gcrypt hash) --8<---------------cut here---------------end--------------->8--- Well, it seems reasonable, IMHO, to assume that an user diving into such internal would be able to parse this information. Cheers, simon
