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 23:09:08 +0100 [thread overview]
Message-ID: <CAMFYt2YJmJ+XbAJf+F2bwKEfJ82kYCyNc=DgOoxPB_PXvHwdjA@mail.gmail.com> (raw)
In-Reply-To: <8338n441qe.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
2013/11/10 Eli Zaretskii <eliz@gnu.org>
> > Date: Sun, 10 Nov 2013 10:16:51 +0100
> > From: Panicz Maciej Godek <godek.maciek@gmail.com>
> > Cc: "guile-user@gnu.org" <guile-user@gnu.org>
> >
> > 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
>
> Then I guess you will have to run that compilation under GDB and see
> why it thinks utf8 is invalid encoding. (Is it really "utf8" or
> "utf-8" or maybe "UTF-8"?)
>
Well, I think that is the reason of the problem -- that for some reason
Windows reports "utf8" encoding, while iconv requires it to be "UTF-8".
If I only knew where exactly is the encoding set to "utf8", I could try
to fix that. (I think that the problem appears only with applications
compiled with -mwindows flag).
However, it turned out that this problem is only superficial -- it appears
when Guile is trying to print backtrace caused by other problems resulting
from the differences in the execution environment (lack of certan libraries,
mostly).
Although it would be helpful to have more feedback from the interpreter,
I think that I should manage to provide all the necessary fixes without it.
[-- Attachment #2: Type: text/html, Size: 2087 bytes --]
next prev parent reply other threads:[~2013-11-10 22:09 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
2013-11-10 17:15 ` Eli Zaretskii
2013-11-10 22:09 ` Panicz Maciej Godek [this message]
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='CAMFYt2YJmJ+XbAJf+F2bwKEfJ82kYCyNc=DgOoxPB_PXvHwdjA@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).