From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libintl static linking issues - yet another spin
Date: Mon, 3 Apr 2017 13:01:49 +0200 [thread overview]
Message-ID: <20170403130149.6ccffe4e@free-electrons.com> (raw)
In-Reply-To: <66e02263-8faf-0601-e3ba-18501de7c6ef@mind.be>
Hello,
[ Not read/thought about the entire e-mail yet, but just one point ]
On Mon, 3 Apr 2017 12:42:21 +0200, Arnout Vandecappelle wrote:
> However, thinking a bit more about it: if libintl support disappears from
> uClibc-ng
What makes you think libintl disappears from uClibc-ng? uClibc-ng has
recently *added* libintl support.
Basically, today we have the following situation:
* glibc comes with its own libintl implementation, which is
full-featured
* uClibc-ng until recently did not have any libintl implementation, so
we are building the libintl from gettext to get a libintl
implementation. uClibc-ng has recently added a stub libintl
implementation, which does not support translation, i.e it's really
just a stub.
* musl has a libintl implementation. It is not a stub, and seems to
support translation (i.e it seems to read .mo files for
translations, etc.).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-03 11:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 21:53 [Buildroot] Patchwork cleanup, 10 patches to look at Thomas Petazzoni
2017-03-27 12:35 ` Arnout Vandecappelle
2017-03-27 13:43 ` Andrey Smirnov
2017-03-28 20:25 ` Thomas Petazzoni
2017-04-03 10:42 ` [Buildroot] libintl static linking issues - yet another spin Arnout Vandecappelle
2017-04-03 11:01 ` Thomas Petazzoni [this message]
2017-04-03 11:25 ` Arnout Vandecappelle
2017-04-03 12:11 ` Thomas Petazzoni
2017-04-03 12:30 ` Waldemar Brodkorb
2017-04-03 12:45 ` Arnout Vandecappelle
2017-04-03 13:02 ` Thomas Petazzoni
2017-04-03 14:12 ` Arnout Vandecappelle
2017-04-01 16:52 ` [Buildroot] Patchwork cleanup, 10 patches to look at Thomas Petazzoni
2017-04-02 3:04 ` Carlos Santos
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=20170403130149.6ccffe4e@free-electrons.com \
--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