Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9336] Improve iconv support for external toolchain based builds
Date: Sun, 23 Oct 2016 13:09:52 +0000	[thread overview]
Message-ID: <bug-9336-163-TumnD7hq4l@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9336-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9336

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
There is already a Buildroot option to copy gconv modules to the target, it
just seems you missed it. In the toolchain menu, when a glibc toolchain is
used, you have:

  [*] Copy gconv libraries
  ()    Gconv libraries to copy

If you leave the second option empty, all gconv modules are copied to the
target. Otherwise, if it's non-empty, only the specified list of gconv modules
are copied.

I've just tested again today, leaving the list empty. Indeed, all gconv modules
are copied, and a simple C program that converts an UTF-8 string to CP1251
using iconv_open() / iconv() works just fine on the target.

The iconv binary itself is however indeed not copied. Maybe we should add an
option to copy additional binaries from the toolchain to the target? Could you
submit such a patch?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2016-10-23 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 15:56 [Buildroot] [Bug 9336] New: Improve iconv support for external toolchain based builds bugzilla at busybox.net
2016-10-23 13:09 ` bugzilla at busybox.net [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=bug-9336-163-TumnD7hq4l@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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