unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: wolf <wolf@wolfsden.cz>
To: help-guix@gnu.org
Subject: guile: Unbound variable: spawn
Date: Wed, 22 Mar 2023 18:52:09 +0100	[thread overview]
Message-ID: <ZBtASYvAIrSSMJLv@ws> (raw)

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

Hi,

I'm trying to call my own guile script from a guix shell, and I'm getting error
about `spawn' not being bound. I simplified the reproduction to a simple
example:

    /tmp/x $ guix shell --container -m manifest.scm -- guile -c spawn
    Backtrace:
    In ice-9/boot-9.scm:
      1752:10  7 (with-exception-handler _ _ #:unwind? _ # _)
    In unknown file:
               6 (apply-smob/0 #<thunk 7f380b4ee0c0>)
    In ice-9/boot-9.scm:
        724:2  5 (call-with-prompt ("prompt") #<procedure 7f380b501d40 ?> ?)
    In ice-9/eval.scm:
        619:8  4 (_ #(#(#<directory (guile-user) 7f380b4f4c80>)))
    In ice-9/command-line.scm:
       185:18  3 (_ #<input: string 7f380b4ed850>)
    In unknown file:
               2 (eval spawn #<directory (guile-user) 7f380b4f4c80>)
    In ice-9/eval.scm:
       223:20  1 (proc #<directory (guile-user) 7f380b4f4c80>)
    In unknown file:
               0 (%resolve-variable (7 . spawn) #<directory (guile-user)?>)
    
    ERROR: In procedure %resolve-variable:
    Unbound variable: spawn

The manifest.scm is:

    (use-modules (gnu packages guile)
    	     (guix packages))
    
    (packages->manifest (list guile-3.0))

Now, when I use guile-3.0-latest it *does* work. So, here comes couple of
questions:

1. Why does not it work with guile-3.0 package?
2. Why is there both guile-3.0 (3.0.7) and guile-3.0-latest (3.0.9)? The comment
   in the source code suggests that 3.0.7 (guile-3.0) is "latest Guile stable
   version", but on https://www.gnu.org/software/guile/ I see nothing to
   indicate that 3.0.8 and 3.0.9 should be considered unstable or experimental
   releases. So I'm bit confused here.
3. How can I make it work with 3.0.7? (Pure curiosity, 3.0.9 works fine for me.)

Thanks :)

W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

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

                 reply	other threads:[~2023-03-22 17:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZBtASYvAIrSSMJLv@ws \
    --to=wolf@wolfsden.cz \
    --cc=help-guix@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.
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).