unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: guile+iconv fails on windows
Date: Sun, 10 Nov 2013 19:15:37 +0200	[thread overview]
Message-ID: <8338n441qe.fsf@gnu.org> (raw)
In-Reply-To: <CAMFYt2Yj1mwN4Km3AGh=FgcbB6krZweboN3WwjBb7dSfjRdX7A@mail.gmail.com>

> 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"?)

> (I believe that since those are dlls and libguile plainly depends on
> libiconv-2.dll, there should be no need to rebuild guile
> afterwards?)

If you rebuilt libiconv-2.dll, you shouldn't need to rebuild guile.



  reply	other threads:[~2013-11-10 17:15 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 [this message]
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=8338n441qe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=godek.maciek@gmail.com \
    --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).