From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33999@debbugs.gnu.org, Bryan Ferris <saffsnail@gmail.com>
Subject: bug#33999: CP437: Invalid Argument on init
Date: Wed, 16 Jan 2019 12:00:15 +0100 [thread overview]
Message-ID: <87tvi8vpds.fsf@gnu.org> (raw)
In-Reply-To: <20190109200804.5619d668@scratchpost.org> (Danny Milosavljevic's message of "Wed, 9 Jan 2019 20:08:04 +0100")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> apparently the message is printed by fsck.fat and is harmless (although we should
> still fix it).
The statically-linked ‘fsck.fat’ doesn’t have access to gconv module,
which is why ‘iconv_open’ would fail.
Glibc has the ability to bring in statically-linked gconv modules, so we
could in theory build a custom glibc for the statically-linked
‘fsck.fat’, but that doesn’t sound great.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2019-01-16 11:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 19:34 bug#33999: CP437: Invalid Argument on init Bryan Ferris
2019-01-09 19:08 ` Danny Milosavljevic
2019-01-09 21:18 ` Bryan Ferris
[not found] ` <CABkR=SUyCV7d6sR1Zyy4Aj4Cp5raS_Tn-Akji3k0fQPeneErFg@mail.gmail.com>
2019-01-10 15:15 ` Bryan Ferris
2019-01-10 17:59 ` Danny Milosavljevic
2019-01-10 20:37 ` Bryan Ferris
2019-01-16 11:00 ` Ludovic Courtès [this message]
2019-01-18 22:59 ` Danny Milosavljevic
2019-01-19 10:19 ` Ludovic Courtès
2019-01-21 0:40 ` Danny Milosavljevic
2019-01-21 8:41 ` Danny Milosavljevic
2019-01-21 9:50 ` Ludovic Courtès
2019-01-21 10:16 ` Danny Milosavljevic
2019-01-21 10:51 ` Ludovic Courtès
2019-01-23 15:42 ` Bryan Ferris
2019-01-26 17:32 ` Bryan Ferris
2019-01-10 18:21 ` Danny Milosavljevic
2019-01-16 15:43 ` Bryan Ferris
2019-01-18 19:00 ` Bryan Ferris
2019-01-18 22:48 ` Danny Milosavljevic
[not found] ` <CABkR=SWtHUA+G50fR_QiU-tGU6TatQ7wnKWW+n6LdFexSYJZRA@mail.gmail.com>
[not found] ` <20190120031949.2bb81997@scratchpost.org>
2019-01-20 14:34 ` Bryan Ferris
2019-01-20 22:48 ` Danny Milosavljevic
2019-01-20 22:49 ` Danny Milosavljevic
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvi8vpds.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33999@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=saffsnail@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).