unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Advice about guile-spec package definition
Date: Thu, 1 Apr 2021 15:17:23 +0300	[thread overview]
Message-ID: <YGW50397Tg4pKVSb@3900XT> (raw)
In-Reply-To: <ce32d54dd9b1299b0c7bb2c767283039a2953028.camel@korwin-zmijowski.fr>

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

On Thu, Apr 01, 2021 at 01:21:10PM +0200, Jérémy Korwin-Zmijowski wrote:
> Le jeudi 01 avril 2021 à 13:16 +0300, Efraim Flashner a écrit :
> > I'm not sure what all it affects, but there does seem to be a
> > difference
> > between guile-3.0.2 and 3.0.5. I'd add guile or leave it out of the
> > environment file depending on which version you want.
> 
> Using the user's Guile version should be fine, so I left it out. But
> then…
> 
> $ guix build -f guix.scm
> […]
> starting phase `build'
> Backtrace:
>            8 (primitive-load "/gnu/store/2l1dkrsvkc5fzng4fj2yndjvb03…")
> In ice-9/eval.scm:
>    191:35  7 (_ _)
> In guix/build/gnu-build-system.scm:
>     838:2  6 (gnu-build #:source _ #:outputs _ #:inputs _ #:phases . #)
> In ice-9/boot-9.scm:
>   1736:10  5 (with-exception-handler _ _ #:unwind? _ # _)
> In srfi/srfi-1.scm:
>    857:16  4 (every1 #<procedure 7ffff4b2dd60 at guix/build/gnu-bui…>
> …)
> In guix/build/gnu-build-system.scm:
>    847:30  3 (_ _)
> In guix/build/guile-build-system.scm:
>    149:21  2 (build #:outputs _ #:inputs _ #:native-inputs _ # _ # _ …)
> In unknown file:
>            1 (string-append "/gnu/store/a80yx2xza2k4i9bwbcsa2vwdjnx…"
> …)
> In ice-9/boot-9.scm:
>   1669:16  0 (raise-exception _ #:continuable? _)
> 
> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
> In procedure string-append: Wrong type (expecting string): #f
> […]
> 
> I don't understant a word of it haha.

It's expecting a string, likely part of (string-append (assoc-ref input
"guile") "/bin/guile"), probably from the guile-build-system. But if
there is no input named "guile" then (assoc-ref input "guile") returns
'#f' so that's what the error means.

Looks like you should put guile back into the guix.scm :)


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-01 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 21:13 Advice about guile-spec package definition Jérémy Korwin-Zmijowski
2021-04-01  7:22 ` Efraim Flashner
2021-04-01  9:39   ` Jérémy Korwin-Zmijowski
2021-04-01 10:16     ` Efraim Flashner
2021-04-01 11:21       ` Jérémy Korwin-Zmijowski
2021-04-01 12:17         ` Efraim Flashner [this message]
2021-04-01 13:09           ` Jérémy Korwin-Zmijowski

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=YGW50397Tg4pKVSb@3900XT \
    --to=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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.
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).