From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/RFC 1/1] package/libiconv: enable extra encodings
Date: Wed, 29 Jan 2020 11:50:49 +0100 [thread overview]
Message-ID: <20200129115049.313f6d6a@windsurf> (raw)
In-Reply-To: <20200128222140.367045-1-bernd.kuhls@t-online.de>
On Tue, 28 Jan 2020 23:21:40 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Quoting https://www.gnu.org/software/libiconv/
>
> "When configured with the option --enable-extra-encodings, it also
> provides support for a few extra encodings:
>
> European languages
> CP{437,737,775,852,853,855,857,858,860,861,863,865,869,1125}
> Semitic languages
> CP864
> Japanese
> EUC-JISX0213, Shift_JISX0213, ISO-2022-JP-3
> Chinese
> BIG5-2003 (experimental)
> Turkmen
> TDS565
> Platform specifics
> ATARIST, RISCOS-LATIN1"
>
> Updating Kodi from version 17.6 to 18.5 caused runtime errors on systems
> with locale support disabled, here Kodi uses libiconv but needs CP437:
>
> ERROR: customConvert: iconv_open() for "CP437" -> "UTF-8" failed,
> errno = 22 (Invalid argument)
>
> The size of libiconv.so.2.6.0 grows from 941K to 1,1M.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
In the Kodi use case, a size increase of 160 KB is not important
obviously, but libiconv is also used in other situations where size
might matter. I don't have a very strongly formed opinion on this, but
perhaps this is a case where a Config.in sub-option might be useful,
which would be selected by Kodi. Please wait a bit for others feedback
before implementing this though, as others may disagree.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-29 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 22:21 [Buildroot] [PATCH/RFC 1/1] package/libiconv: enable extra encodings Bernd Kuhls
2020-01-29 10:50 ` Thomas Petazzoni [this message]
2020-02-01 10:52 ` Arnout Vandecappelle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200129115049.313f6d6a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.