From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with iconv_open and Linaro toolchain
Date: Thu, 11 Jul 2013 12:56:01 +0200 [thread overview]
Message-ID: <20130711125601.75b219f6@skate> (raw)
In-Reply-To: <51DE78F4.9050705@wanadoo.fr>
Dear Thierry Bultel,
On Thu, 11 Jul 2013 11:20:52 +0200, Thierry Bultel wrote:
> The /usr/lib/arm-linux-gnueabihf does not exist at all on the target,
> but only in the sysroot.
> Copying it manually solves the issue, but I do not feel comfortable with
> having a piece
> of the toolchain path on my system...
>
> What is your point of view about this ? What would be the right way to do ?
The right way is to add a Buildroot option that copies certain gconv
modules, which are needed on (e)glibc toolchains to make iconv work
properly, and maybe generates the gconv-modules.cache (this is done
using iconvconfig, we'd have to see how to get this tool, or package
it).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-11 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:20 [Buildroot] Issue with iconv_open and Linaro toolchain Thierry Bultel
2013-07-11 10:56 ` Thomas Petazzoni [this message]
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=20130711125601.75b219f6@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