From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: guile+iconv fails on windows
Date: Sun, 10 Nov 2013 10:16:51 +0100 [thread overview]
Message-ID: <CAMFYt2Yj1mwN4Km3AGh=FgcbB6krZweboN3WwjBb7dSfjRdX7A@mail.gmail.com> (raw)
In-Reply-To: <837gcg534b.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Hi!
> > ;;; compiling .\extra\common.scm
> > ;;; compiling c:/guile2/share/guile/2.0\system\vm\frame.scm
> > Backtrace:
> > In unknown file:
> > ?: 1 ;;; compiling system\vm\frame.scm
> > Exception thrown while printing backtrace:
> > ERROR: In procedure open_iconv_descriptors: invalid or unknown character
> > encoding "utf8"
> >
> > Do you know what could be the reason and solution?
> > Should I rebuild libiconv and then relink guile against it?
> > Would that work? Or is there any quick workaround?
>
> Assuming you link against libiconv as DLL, then if you run the
> dependency walker on your libiconv DLL, does it show that it depends
> on libgcc DLL? If so, try a version of libiconv that doesn't depend
> on libgcc, or build libiconv yourself that way.
>
The dependency walker shows that libiconv depends only on dlls supplied
by Windows (kernel32.dll, msvcrt.dll and ntdll.dll). The dependency on
libgcc appears only in libguile, but it seems to have nothing to do with
iconv. Rebuilding libiconv didn't change anything (I believe that since
those are dlls and libguile plainly depends on libiconv-2.dll, there should
be no need to rebuild guile afterwards?)
[-- Attachment #2: Type: text/html, Size: 1626 bytes --]
next prev parent reply other threads:[~2013-11-10 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 22:35 guile+iconv fails on windows Panicz Maciej Godek
2013-11-10 3:48 ` Eli Zaretskii
2013-11-10 9:16 ` Panicz Maciej Godek [this message]
2013-11-10 17:15 ` Eli Zaretskii
2013-11-10 22:09 ` Panicz Maciej Godek
2013-11-11 3:45 ` Eli Zaretskii
2013-11-11 11:45 ` Panicz Maciej Godek
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='CAMFYt2Yj1mwN4Km3AGh=FgcbB6krZweboN3WwjBb7dSfjRdX7A@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=eliz@gnu.org \
--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).