From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: Re: Using guile-scmutils with REPL and compilation
Date: Sat, 20 Jun 2020 10:33:34 +0300 [thread overview]
Message-ID: <20200620073334.GA1894@newvzh.lokolhoz> (raw)
In-Reply-To: <CAJN5JQqG-2U99Xt40RHamAncrJhkkv_KijS2=zrsOVQq0_6u4Q@mail.gmail.com>
Hi Slava,
On Sat, Jun 20, 2020 at 02:43:00AM +0300, Viacheslav Dushin wrote:
...
> Second one:
> There is also a problem with code compilation:
>
> (load (%search-load-path "guile-scmutils/src/load.scm"))
> (set-current-module generic-environment)
>
> (define ((Gamma w) t)
> (up t (w t) ((D w) t)))
>
> works fine in the REPL, but fails to compile (guile code.scm) with the
> following error:
>
> ;;; note: source file
> /usr/local/Cellar/guile/2.2.7_2/share/guile/2.2/ice-9/boot-9.scm
> ;;; newer than compiled
> /usr/local/Cellar/guile/2.2.7_2/lib/guile/2.2/ccache/ice-9/boot-9.go
> ;;; note: source file
> /Users/slava/Documents/work/func-diff-geometry/prologue/code.scm
> ;;; newer than compiled
> /Users/slava/.cache/guile/ccache/2.2-LE-8-3.A/Users/slava/Documents/work/func-diff-geometry/prologue/code.scm.go
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;; or pass the --no-auto-compile argument to disable.
> ;;; compiling /Users/slava/Documents/work/func-diff-geometry/prologue/code.scm
> ;;; WARNING: compilation of
> /Users/slava/Documents/work/func-diff-geometry/prologue/code.scm
> failed:
> ;;; Syntax error:
> ;;; /Users/slava/Documents/work/func-diff-geometry/prologue/code.scm:4:0:
> source expression failed to match any pattern in form (define ((Gamma
> w) t) (up t (w t) ((D w) t)))
> Backtrace:
> 6 (primitive-load "/Users/slava/Documents/work/func-diff-…")
> 5 (_ #<procedure 102790fe0 at ice-9/eval.scm:330:13 ()> # #)
> 4 (_ #<procedure 102790ec0 at ice-9/eval.scm:330:13 ()> # #)
> 3 (_ #<procedure 102790de0 at ice-9/eval.scm:330:13 ()> # #)
> In ice-9/eval.scm:
> 245:16 2 (_ #(#(#<module (guile) 102695dc0> #f #<variable 10…> …)))
> In unknown file:
> 1 (string-prefix? "/" #f #<undefined> #<undefined> #<und…> …)
> 0 (_ #<procedure 102790b20 at ice-9/eval.scm:330:13 ()> # #)
>
> ERROR: In procedure string-prefix?: Wrong type argument in position 2
> (expecting string): #f
Try
(load #f)
and you'll get the same error.
`load' requires string as an argument. AFAICS in the Guile
reference manual, probably the function is supposed to work in
REPL only (while it works without it).
If `%search-load-path' is not able to find the file you want to
load, it returns #f. You can check your `%load-path' if the
directory with that file is listed in that variable. If not, use
`add-to-load-path "the-dir-your-file-resides-in"' to make it work,
or use the absolute path of the file.
HTH
--
Vladimir
(λ)επτόν EDA — https://github.com/lepton-eda
next prev parent reply other threads:[~2020-06-20 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 23:43 Using guile-scmutils with REPL and compilation Viacheslav Dushin
2020-06-20 7:33 ` Vladimir Zhbanov [this message]
2020-07-04 14:57 ` Vladimir Zhbanov
2020-07-08 21:04 ` Viacheslav Dushin
2020-07-09 6:32 ` Vladimir Zhbanov
-- strict thread matches above, loose matches on Subject: below --
2020-06-20 14:39 Viacheslav Dushin
2020-07-04 1:06 Viacheslav Dushin
2020-07-04 4:15 ` Catonano
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200620073334.GA1894@newvzh.lokolhoz \
--to=vzhbanov@gmail.com \
--cc=guile-user@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).