From: Stanislav Vasic <svlasic@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] iconv: additional encodings
Date: Fri, 1 Nov 2013 20:10:33 +0000 (UTC) [thread overview]
Message-ID: <l511rp$p7$1@ger.gmane.org> (raw)
In-Reply-To: 20131101175255.162ae15b@skate
Hi Thomas,
I believe Jan is talking about my patch:
https://github.com/Stane1983/buildroot-mx/
commit/8be22b0db136403ee55c84bf093366808d65dc3f
It works for Linaro toolchains.
In this patch I had to export GCONV_PATH because of XBMC. Otherwise, XBMC
is not aware of gconv libs existence.
On Fri, 01 Nov 2013 17:52:55 +0100, Thomas Petazzoni wrote:
> Dear Jan Pohanka,
>
> On Fri, 1 Nov 2013 17:44:31 +0100, Jan Pohanka wrote:
>
>> I will prepare a patch with this feature. Can you please confirm
>> whether /etc/environment file can be used to set variables for whole
>> system in Busybox? Or it is better to use eg. profile file, etc.
>
> Why is setting an environment variable necessary? Isn't glibc always
> looking for gconv modules in a standard place, in which we could install
> those modules?
>
> Thomas
next prev parent reply other threads:[~2013-11-01 20:10 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
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 [this message]
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='l511rp$p7$1@ger.gmane.org' \
--to=svlasic@gmail.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