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 11096] Upgrade from glibc 2.26 to 2.27 broke some locales (ru_RU in particular)
Date: Sun, 01 Jul 2018 18:05:47 +0000	[thread overview]
Message-ID: <bug-11096-163-ZFQ9qPjK51@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11096-163@https.bugs.busybox.net/>

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

--- Comment #2 from romain.naour at gmail.com ---
Hi,

So, we really have a problem with host-localedef...

Our current version is outdated (based on eglibc) and doesn't work with glibc
2.26. Localedef package version should be the same as glibc package because
localedef program is part of glibc and building it require glibc sources.

Yocto and ptxdist maintain some "hack/workaround" to only build localedef for
the host [1] [2].

Also, pre compiled toolchain doesn't provide localdef binary for the host along
with glibc provided for the target.

I'm not sure if we should allow using BR2_GENERATE_LOCALE for external
toolchains since there is no guaranties that localedef is compatible with
toolchain locale.

Best regards,
Romain

[1]
https://git.pengutronix.de/cgit/ptxdist/tree/patches/localedef-glibc-2.27/0001-HACK-only-build-and-install-localedef.patch

[2] git://github.com/kraj/localedef and
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/recipes-core/glibc/cross-localedef-native_2.26.bb?id=rocko-18.0.3

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

  parent reply	other threads:[~2018-07-01 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:53 [Buildroot] [Bug 11096] New: Upgrade from glibc 2.26 to 2.27 broke some locales (ru_RU in particular) bugzilla at busybox.net
2018-06-30 19:58 ` [Buildroot] [Bug 11096] " bugzilla at busybox.net
2018-06-30 21:45 ` bugzilla at busybox.net
2018-07-01 18:05 ` bugzilla at busybox.net [this message]
2018-08-04 17:04 ` bugzilla at busybox.net
2019-05-23 17:57 ` bugzilla at busybox.net
2019-06-19 11:42 ` bugzilla at busybox.net

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-11096-163-ZFQ9qPjK51@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