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: Sat, 30 Jun 2018 21:45:42 +0000	[thread overview]
Message-ID: <bug-11096-163-35rSviXUOa@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 #1 from romain.naour at gmail.com ---
Hi,

Are you sure that Buildroot is using localedef from the host?
Buildroot is building it's own localedef version from [1] which is probably too
old for glibc 2.27.
Maybe we have to bump localedef to [2] which is used by Yocto?

localedef is build by the glibc package but for the target, so we really need
to build it outside of glibc package.

Best regards,
Romain

[1]
http://www.pengutronix.de/software/ptxdist/temporary-src/localedef-eglibc-2.14.1-r17443-ptx1.tar.bz2

[2] git://github.com/kraj/localedef

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

  parent reply	other threads:[~2018-06-30 21:45 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 [this message]
2018-07-01 18:05 ` bugzilla at busybox.net
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-35rSviXUOa@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