From: Christopher Baines <mail@cbaines.net>
To: Guile User <guile-user@gnu.org>
Subject: Debugging Guile module loading
Date: Mon, 12 Mar 2018 19:25:15 +0000 [thread overview]
Message-ID: <87h8pl9jvo.fsf@cbaines.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hey,
I'm having some trouble with Guile module loading. I've got a
(use-modules ...) call which results in some warnings, which seem to be
actually more like errors, as the modules aren't loaded.
From loading one module, I get two errors in the form:
warning: failed to load '...':
Unbound variable: ...
The modules and variables all exist, but as far as I understand Guile
modules, they shouldn't be required for loading the module requested.
Any tips on debugging use-modules? Initially it would be good to work
out what modules it's attempting to load.
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next reply other threads:[~2018-03-12 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 19:25 Christopher Baines [this message]
2018-03-12 20:40 ` Debugging Guile module loading Mike Gran
2018-03-13 16:57 ` Mark H Weaver
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=87h8pl9jvo.fsf@cbaines.net \
--to=mail@cbaines.net \
--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).