From: cong gu <gucong43216@gmail.com>
To: Ian Price <ianprice90@googlemail.com>, guile-user@gnu.org
Subject: Re: guildhall packages
Date: Wed, 29 Aug 2012 08:25:59 -0500 [thread overview]
Message-ID: <CAH_4JjNDjLUMa+XT6NYdfmrAftsr1MnNNZmPG96mfqTJ3sBXzw@mail.gmail.com> (raw)
In-Reply-To: <87d329x3eu.fsf@Kagami.home>
Hi,
In guildhall, I can use other packages, but there are two problems
with package 'srfi'.
The first is I have to add 'sls' to %load-extensions. This is easy.
The second is that the filenames seem not compatible with guile's
module searching.
For example it is 'srfi/%3a41.sls' instead of guile's way like
'srfi/srfi-41.sls'
scheme@(guile-user)> (use-modules (srfi srfi-41))
While compiling expression:
ERROR: no code for module (srfi srfi-41)
How to make them work?
--
Cong Gu
next prev parent reply other threads:[~2012-08-29 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 1:01 guildhall packages Ian Price
2012-08-26 21:29 ` Ludovic Courtès
2012-08-26 21:34 ` Noah Lavine
2012-08-29 12:56 ` Ian Price
2012-08-29 13:25 ` cong gu [this message]
2012-08-29 16:42 ` Ian Price
2012-08-26 21:54 ` Julian Graham
2012-08-29 11:46 ` Ian Price
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=CAH_4JjNDjLUMa+XT6NYdfmrAftsr1MnNNZmPG96mfqTJ3sBXzw@mail.gmail.com \
--to=gucong43216@gmail.com \
--cc=guile-user@gnu.org \
--cc=ianprice90@googlemail.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).