From: Paul Smith <psmith@gnu.org>
To: guile-user@gnu.org
Subject: Errors using Guile 2.0 vs. Guile 1.8
Date: Sun, 29 Jan 2012 10:54:18 -0500 [thread overview]
Message-ID: <1327852458.3401.10.camel@homebase> (raw)
Hi all.
To test my GNU make Guile integration I was using guile 1.8 which is
what my distribution provided. To test the newer Guile 2.x I downloaded
the Guile 2.0.3 release and built it and installed in an alternate
location (/opt/guile). I compiled GNU make using that version, and all
the tests ultimately work BUT whenever I use (define ...) from within
GNU make I get these errors:
$ cat g1.mk
define show
(define (show s)
(display s)
(newline))
endef
$(info define display)
$(guile $(show))
$(info after define)
$(guile (show "HI"))
all:;
$ make -f g1.mk
define display
Backtrace:
In ice-9/boot-9.scm:
162: 5 [catch #t #<catch-closure 1cb55c0> ...]
170: 4 [#<procedure 1cb8cd0 ()>]
In unknown file:
?: 3 [catch-closure]
In ice-9/eval.scm:
389: 2 [eval # #]
374: 1 [eval # #]
In unknown file:
?: 0 [scm-error misc-error #f ...]
ERROR: In procedure scm-error:
ERROR: Unknown object: #<variable 1cd0180 value: #<procedure 1cb95a0 at ice-9/eval.scm:378:13 (a)>>
after define
HI
make: `all' is up to date.
I don't know what this means, or how to proceed with debugging. The
same code works fine with Guile 1.8.
Did I make a mistake with my build or install of Guile 2.0.3?
Thoughts?
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@gnu.org> Find some GNU make tips at:
http://www.gnu.org http://make.mad-scientist.net
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
next reply other threads:[~2012-01-29 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 15:54 Paul Smith [this message]
2012-01-29 21:18 ` Errors using Guile 2.0 vs. Guile 1.8 Thien-Thi Nguyen
2012-01-29 21:51 ` Paul Smith
2012-01-29 22:26 ` Mark H Weaver
2012-01-29 22:57 ` Mark H Weaver
2012-01-30 0:17 ` Paul Smith
2012-01-30 1:16 ` Mark H Weaver
2012-01-30 1:42 ` Paul Smith
2012-01-30 11:06 ` Andy Wingo
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=1327852458.3401.10.camel@homebase \
--to=psmith@gnu.org \
--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).