All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] musl/gettext issue
Date: Tue, 26 Jan 2016 22:29:58 +0100	[thread overview]
Message-ID: <20160126222958.63f31eb2@free-electrons.com> (raw)
In-Reply-To: <nq4lncxo36.ln2@ID-313208.user.individual.net>

Hello,

On Tue, 26 Jan 2016 22:25:11 +0100, Bernd Kuhls wrote:
> Am Wed, 16 Sep 2015 22:16:36 +0200 schrieb Thomas Petazzoni:
> 
> > Now, enter musl. It does have an internal gettext implementation.
> > However, it is not recognized by GNU gettext has a correct
> > implementation, so when you build GNU gettext in a musl system, it does
> > build/install libintl.so and its header files.
> 
> Hi Thomas,
> 
> is there already a solution for this problem?

No, I personally haven't had the time to work on this topic, and nobody
else did, apparently.

> I saw the bug with aumix-2.8 which I could solve by bumping the package 
> to 2.9.1. Now I am stuck with http://autobuild.buildroot.net/?reason=gdk-
> pixbuf-2.32.3
> 
> Is this bug report related to our problem?
> http://savannah.gnu.org/bugs/?46436

Yes, it seems related, at least it reflects very well the fact that
musl provides a gettext implementation, but gettext.m4 doesn't
recognize it as being a valid implementation.

I see
http://lists.gnu.org/archive/html/bug-gettext/2015-04/msg00002.html
hasn't got much feedback on the gettext mailing list, so we'll probably
have to dig into the topic ourselves, and find some solution.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-01-26 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 20:16 [Buildroot] musl/gettext issue Thomas Petazzoni
2015-09-17 22:27 ` Arnout Vandecappelle
2015-09-18  7:41   ` Thomas Petazzoni
2015-09-18 14:00     ` Arnout Vandecappelle
2015-10-04  9:30   ` Peter Korsgaard
2015-10-11 21:21 ` Jörg Krause
2016-01-15  1:19 ` Jörg Krause
2016-01-26 21:25 ` Bernd Kuhls
2016-01-26 21:29   ` Thomas Petazzoni [this message]
2016-01-30 22:52     ` Bernd Kuhls

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=20160126222958.63f31eb2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.