All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Khem Raj <raj.khem@gmail.com>, Joshua Watt <jpewhacker@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glibc: Fix locale DEPENDS
Date: Mon, 1 Jul 2019 23:13:27 +0000	[thread overview]
Message-ID: <e6cf5479e8da4d7e95463096a50b820e@xbox06.axis.com> (raw)
In-Reply-To: <CAMKF1srnRNisnxfnhypBQuwO9F5q72LSDzuBZqdStBoXaR1kDQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]

Are you thinking of gettext-minimal-native? It is used by gettext.bbclass if USE_NLS is “no”.

//Peter

From: openembedded-core-bounces@lists.openembedded.org <openembedded-core-bounces@lists.openembedded.org> On Behalf Of Khem Raj
Sent: den 28 juni 2019 18:37
To: Joshua Watt <jpewhacker@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] glibc: Fix locale DEPENDS



On Thu, Jun 27, 2019 at 9:54 AM Joshua Watt <jpewhacker@gmail.com<mailto:jpewhacker@gmail.com>> wrote:
gettext is required to generate the glibc locales in do_compile. If not
present, glibc will skip the generation which isn't reproducible.

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com<mailto:JPEWhacker@gmail.com>>
---
 meta/recipes-core/glibc/glibc_2.29.bb<http://glibc_2.29.bb> | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/glibc/glibc_2.29.bb<http://glibc_2.29.bb> b/meta/recipes-core/glibc/glibc_2.29.bb<http://glibc_2.29.bb>
index 073d1533e37..c400ee10b0f 100644
--- a/meta/recipes-core/glibc/glibc_2.29.bb<http://glibc_2.29.bb>
+++ b/meta/recipes-core/glibc/glibc_2.29.bb<http://glibc_2.29.bb>
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://LICENSES;md5=cfc0ed77a9f62fa62eded042ebe31d72 \
       file://posix/rxspencer/COPYRIGHT;md5=dc5485bb394a13b2332ec1c785f5d83a \
       file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c<file://LICENSES;md5=cfc0ed77a9f62fa62eded042ebe31d72%20/%0b %20 %20 %20 file:/posix/rxspencer/COPYRIGHT;md5=dc5485bb394a13b2332ec1c785f5d83a%20/%0b %20 %20 %20 file:/COPYING.LIB;md5=4fbd65380cdd255951079008b364516c>"

-DEPENDS += "gperf-native bison-native make-native"
+DEPENDS += "gperf-native bison-native make-native gettext-native"

I think we have had this dependency proposed in past and one think that worries me is that it will cause serialization a bit more and can affect bulls times wasn’t there a minimal gettext at some point and I wonder if that could satisfy needs here


 PV = "2.29"

--
2.21.0

[-- Attachment #2: Type: text/html, Size: 5981 bytes --]

  reply	other threads:[~2019-07-01 23:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 13:54 [PATCH] glibc: Fix locale DEPENDS Joshua Watt
2019-06-27 16:19 ` Burton, Ross
2019-06-28 13:58   ` Joshua Watt
2019-06-27 19:47 ` Andre McCurdy
2019-06-27 20:15   ` Joshua Watt
2019-06-28 16:37 ` Khem Raj
2019-07-01 23:13   ` Peter Kjellerstedt [this message]
2019-07-02  3:25     ` Khem Raj
2019-08-27 12:50       ` Joshua Watt
  -- strict thread matches above, loose matches on Subject: below --
2019-08-27 12:45 Joshua Watt
2019-08-28 16:09 ` Richard Purdie
2019-08-28 16:27   ` Joshua Watt

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=e6cf5479e8da4d7e95463096a50b820e@xbox06.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.