unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
To: Marco Maggi <marco.maggi-ipsu@poste.it>
Cc: Andy Wingo <wingo@pobox.com>, guile-user@gnu.org
Subject: Re: [r6rs] abusive request for help on "unbound variable" error
Date: Sun, 21 Nov 2010 23:12:29 +0100	[thread overview]
Message-ID: <878w0mz5pu.fsf@delenn.lan> (raw)
In-Reply-To: <87r5ef5dtq.fsf@rapitore.luna> (Marco Maggi's message of "Sun, 21 Nov 2010 08:35:29 +0100")

Marco Maggi <marco.maggi-ipsu@poste.it> writes:

> "Andy Wingo" wrote:
>>On Thu 18 Nov 2010 22:25, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
>>
>>>   With      Guile's      master      branch      checkout
>>> 8d10ccae79ff46f0ebea92ba36acfaebafba8d86       on      an
>>> i686-pc-linux-gnu I get the following error:
>>
>> Glad you found your problem in other mails.
>
> I  have  not.  I  was  wrong  regarding  bindings not  being
> re-exported (I forgot what my local scripting infrastructure
> did);  but I  still get  the "unbound  variable"  error from
> Guile.
>
>   The   only   thing   I   can  guess   (after   trying   to
> comment/uncomment random forms) is that it is a problem with
> the expander possibly in its interaction with compiled code,
> because all the other  R6RS implementations work fine.  Also
> I have found this: when  I run the test with "--autocompile"
> (starting with a clean cache) I get the error:
>
> GUILE_LOAD_PATH=. guile -l guile-r6rs-setup.scm --autocompile -s ./tests/test-annotated-types.sps
> ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;       or pass the --no-autocompile argument to disable.
> ;;; compiling guile-r6rs-setup.scm
> [...]
> ;;; WARNING: compilation of ./tests/test-annotated-types.sps failed:
> ;;; key vm-error, throw_args (vm-run "VM: Unbound variable: ~s" (#<variable 851b5e8 value: #<undefined>>))
> guile: uncaught throw to vm-error: (vm-run "VM: Unbound variable: ~s" (#<variable 851b5e8 value: #<undefined>>))
> make: *** [gtest] Error 1
>
Yep, that's the unfortunatly quite non-descriptive error you'll get when
a module exports a binding it does not define.

> but  when  running  with  "--no-autocompile" (with  a  clean
> cache) I get:
>
[...]
> ERROR: Unbound variable: assert
> make: *** [gtest] Error 1
>
> I do use ASSERT in the code, but I do no strange things with
> its binding.   Unfortunately I have  no time to dive  in the
> internals of Scheme implementations.
>
Indeed `assert' is missing from Guile ATM, but I've submitted a patch a
while ago that fixes that (among other things):

<http://lists.gnu.org/archive/html/guile-devel/2010-10/msg00098.html>

I hope that someone gives that patch a review soon (*hint* *hint*)...

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>



  reply	other threads:[~2010-11-21 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 21:25 [r6rs] abusive request for help on "unbound variable" error Marco Maggi
2010-11-19 11:48 ` Marco Maggi
2010-11-19 11:52   ` Marco Maggi
2010-11-20 22:32 ` Andy Wingo
2010-11-21  7:35   ` Marco Maggi
2010-11-21 22:12     ` Andreas Rottmann [this message]
2010-11-21 22:27       ` Andreas Rottmann

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=878w0mz5pu.fsf@delenn.lan \
    --to=a.rottmann@gmx.at \
    --cc=guile-user@gnu.org \
    --cc=marco.maggi-ipsu@poste.it \
    --cc=wingo@pobox.com \
    /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).