From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: Andy Wingo <wingo@pobox.com>, bug-guile@gnu.org
Subject: [bug #28442] Compiler not seeing module define in load-extension
Date: Sun, 03 Jan 2010 11:41:18 +0000 [thread overview]
Message-ID: <20100103-114118.sv20118.11937@savannah.gnu.org> (raw)
In-Reply-To: <20091230-160439.sv0.71152@savannah.gnu.org>
Update of bug #28442 (project guile):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
See discussion in http://article.gmane.org/gmane.lisp.guile.devel/9815.
Closing as invalid, as it appears that the module in question needs to have an
eval-when (or eval-case if 1.8 compatibility is needed). Thanks for the
report, and let us know if you have further problems.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28442>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2010-01-03 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 15:21 [bug #28442] Compiler not seeing module define in load-extension anonymous
2009-12-30 16:04 ` anonymous
2010-01-03 11:41 ` Andy Wingo [this message]
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=20100103-114118.sv20118.11937@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--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).