From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] iconv: additional encodings
Date: Fri, 1 Nov 2013 13:15:57 +0100 [thread overview]
Message-ID: <20131101131557.232faaa6@skate> (raw)
In-Reply-To: <52734FA0.3060508@gmail.com>
Dear Jan Pohanka,
On Fri, 01 Nov 2013 07:52:16 +0100, Jan Pohanka wrote:
> I have realized that external toolchain support is a bit patched in the
> fork that I'm using compared to original one. There is an option to copy
> files gconv-modules, gconv-modules.cache, CP1250.so, and all other
> encodings shared libraries to target/usr/lib/gconv directory. I thought
> that it is a standard directory which the glibc iconv implementation
> would search shared encodings for. This is not truth because GCONV_PATH
> has to be set and point there, to make iconv work with all encodings.
>
> Maybe something similar could be added to standard Buildroot. It took me
> a day to realize where is the problem.
Do you think you could send a patch to implement this in Buildroot?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-01 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 12:50 [Buildroot] iconv: additional encodings Jan Pohanka
[not found] ` < CABMiYf_=RK0UJyZLNkW5JU3xSXKMcNxL9-VRxjNpFqtZ3ye50g@mail.gmail.com>
[not found] ` < 0e99777a-09bf-4414-9769-cbfdd10aa040@email.android.com>
2013-10-31 20:23 ` Jan Pohanka
2013-10-31 20:38 ` Thomas De Schampheleire
2013-11-01 6:52 ` Jan Pohanka
2013-11-01 12:15 ` Thomas Petazzoni [this message]
2013-11-01 16:44 ` Jan Pohanka
2013-11-01 16:52 ` Thomas Petazzoni
[not found] ` < CABMiYf9+4TujbLF8UM7-argbVtmquqgL9we6HRorGEMVA=Qx_w@mail.gmail.com>
[not found] ` < 20131101175255.162ae15b@skate>
2013-11-01 20:10 ` Stanislav Vasic
2013-11-01 22:02 ` Jan Pohanka
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=20131101131557.232faaa6@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox