From: Andy Wingo <wingo@pobox.com>
To: "carlo.bramix" <carlo.bramix@libero.it>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Again on Windows support (2)
Date: Sat, 20 Jun 2009 12:53:48 +0200 [thread overview]
Message-ID: <m3bpoj89c3.fsf@pobox.com> (raw)
In-Reply-To: <KLI2NI$CB1503C245C72AFD0554A91F9105D37B@libero.it> (carlo bramix's message of "Fri, 19 Jun 2009 21:11:42 +0200")
On Fri 19 Jun 2009 21:11, "carlo.bramix" <carlo.bramix@libero.it> writes:
> Under Cygwin, compilation advanced much more with newer sources
> (yeah!)
Cool :)
> but it gave another error:
>
> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o "ice-9/i18n.
> go" "ice-9/i18n.scm"
> Backtrace:
[...]
> ?: 34* [load-extension "libguile-i18n-v-0" "scm_init_i18n"]
>
> <unnamed port>: In procedure dynamic-link in expression (load-extension "libguile-i18n-v-0" "scm_init_i18n"):
> <unnamed port>: file: "libguile-i18n-v-0", message: "can't open the
> module"
Perhaps something is wrong when linking this module. "Can't open the
module" is not a very good warning :)
If you've gotten to here, you might be able to run Guile:
$ meta/guile
If it doesn't error about srfi-1 lib loading, that means you do have
dynamic library loading working, that it's just a problem with the i18n
lib.
Good luck,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-06-20 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 19:11 Again on Windows support (2) carlo.bramix
2009-06-20 10:53 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-01 18:55 carlo.bramix
2009-06-26 18:45 carlo.bramix
2009-06-23 9:41 carlo.bramix
2009-06-22 10:22 carlo.bramix
2009-06-22 9:18 carlo.bramix
2009-06-19 14:17 carlo.bramix
2009-06-19 16:17 ` Ludovic Courtès
2009-06-19 18:30 ` Ludovic Courtès
2009-06-19 8:48 carlo.bramix
2009-06-19 17:58 ` Neil Jerram
2009-06-19 18:09 ` Neil Jerram
2009-06-19 8:15 carlo.bramix
2009-06-19 17:50 ` Neil Jerram
2009-06-16 18:26 carlo.bramix
2009-06-17 20:41 ` Neil Jerram
2009-06-17 21:09 ` Neil Jerram
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=m3bpoj89c3.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=carlo.bramix@libero.it \
--cc=guile-devel@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).