From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11096] New: Upgrade from glibc 2.26 to 2.27 broke some locales (ru_RU in particular)
Date: Tue, 12 Jun 2018 14:53:47 +0000 [thread overview]
Message-ID: <bug-11096-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11096
Bug ID: 11096
Summary: Upgrade from glibc 2.26 to 2.27 broke some locales
(ru_RU in particular)
Product: buildroot
Version: 2018.05
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: psycho_dk at mail.ru
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7646
--> https://bugs.busybox.net/attachment.cgi?id=7646&action=edit
glibc downgrade patch
glibc 2.27 updated some locale definitions (added alt_mon, ab_lat_mon
descriptions). See release notes:
https://sourceware.org/ml/libc-announce/2018/msg00000.html.
Buildroot uses host's localedef for locale compilation. It's foreign utility
for glibc (from eglibc) and it doesn't support new descriptions. It cause error
in the final stage:
> for locale in ru_RU.UTF-8 ; do inputfile=`echo ${locale} | cut -f1 -d'.'` ; charmap=`echo ${locale} | cut -f2 -d'.' -s` ; if test -z "${charmap}" ; then charmap="UTF-8" ; fi ; echo "Generating locale ${inputfile}.${charmap}" ; I18NPATH=/home/hoxnox/devel/buildroot/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/share/i18n:/usr/share/i18n /home/hoxnox/devel/buildroot/output/host/bin/localedef --prefix=/home/hoxnox/devel/buildroot/output/target --"little"-endian -i ${inputfile} -f ${charmap} ${locale} ; done
> Generating locale ru_RU.UTF-8
> /home/hoxnox/devel/buildroot/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/share/i18n/locales/ru_RU:125: LC_TIME: syntax error
> /home/hoxnox/devel/buildroot/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/share/i18n/locales/ru_RU:149: LC_TIME: syntax error
It's also the cause of no locale support by libc in the target system.
Downgrading to glibc-2.26 solves the problem (see attachment), but is not the
solution.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-06-12 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:53 bugzilla at busybox.net [this message]
2018-06-30 19:58 ` [Buildroot] [Bug 11096] Upgrade from glibc 2.26 to 2.27 broke some locales (ru_RU in particular) bugzilla at busybox.net
2018-06-30 21:45 ` bugzilla at busybox.net
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@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