Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "package/gettext-tiny: bump version to add --template option"
Date: Sun, 7 Apr 2019 16:13:25 +0200	[thread overview]
Message-ID: <20190407161325.1d37e578@windsurf> (raw)
In-Reply-To: <20190407135543.GO2659@scaer>

On Sun, 7 Apr 2019 15:55:43 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> I think that, ideally, we would like to have:
>   - libintl headers that expose the same API as those from GNU gettext,
>   - a libintl (probably a static one) that exposes just stub functions.

Is this actually needed ? All of glibc, musl and uclibc provide
libintl.h, and a dummy implementation of libintl functions.

We only need the full-blown gettext on the target to provide libintl
with real functionality when NLS=y and uclibc/musl is used.

But other than that, when !NLS, the stub implementation in musl/uclibc
is fine, no ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-04-07 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07  7:37 [Buildroot] [PATCH] Revert "package/gettext-tiny: bump version to add --template option" Yann E. MORIN
2019-04-07  8:03 ` Vadim Kochan
2019-04-07  8:23 ` James Hilliard
2019-04-07  8:30   ` Yann E. MORIN
2019-04-07  8:45     ` James Hilliard
2019-04-07  8:49       ` Yann E. MORIN
2019-04-07  9:13         ` Vadim Kochan
2019-04-07 13:11 ` Thomas Petazzoni
2019-04-07 13:55   ` Yann E. MORIN
2019-04-07 14:13     ` 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=20190407161325.1d37e578@windsurf \
    --to=thomas.petazzoni@bootlin.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