Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Question] Glibc 2.27+ build and localedef
Date: Tue, 5 Feb 2019 18:33:06 +0100	[thread overview]
Message-ID: <20190205183306.0a563445@gmx.net> (raw)
In-Reply-To: <CABhNV20+Gv6n0hbNK81fNjOcOv3MOTOu_=SOVnZ3ikERo84nmA@mail.gmail.com>

Hello Einar,

On Tue, 5 Feb 2019 18:23:21 +0100, Einar J?n <tolvupostur@gmail.com> wrote:

> Hello guys
> 
> I just upgraded my buildroot from 2017.02 (glibc 2.23) to master
> (glibc 2.28), and I'm having trouble with setlocale.
> $ export LC_ALL=en_US.UTF-8
> -bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
> 
> I think this commit is causing some issues with our old localedef:
> https://github.com/bminor/glibc/commit/58b1a7eaf9099f7db793ecf6718c43ff7f4ec0d4#diff-4ef3edca6b1476bee09d60d0af7e4d1b
> , and some missing fields in en_US locale are also triggering more
> warnings.So the file /usr/lib/locale/locale-archive isn't working as
> it should.
> 
> The host localedef version we are using in buildroot is pretty old
> (eglibc 2.14.1, never bumped since 2012-05-09), but glibc is now at
> 2.28-69.
> 
> I tried to bypass the issue by building host-glibc (which needs
> host-linux-headers) instead of host-localedef, but that's opening a
> whole other can of worms.
> I can copy $(STAGING_DIR)/usr/bin/localedef and
> $(STAGING_DIR)/usr/share/i18n to the target and build a valid
> locale-archive there, but I'd like this to work on the host too.
> 
> Is this a known issue, or is it just me?

Known issue, see e.g.:

[RFC v2] localedef: update to glibc-2.28 and various fixes ([1])

Regards,
Peter

[1] http://lists.busybox.net/pipermail/buildroot/2018-December/237991.html

> --
> Relevant stuff:
> BR2_GCC_TARGET_MODE="arm"
> BR2_TOOLCHAIN_USES_GLIBC=y
> BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
> BR2_PACKAGE_GLIBC=y
> BR2_GCC_VERSION="7.3.0"
> BR2_ENDIAN="LITTLE"
> BR2_EXTRA_GCC_CONFIG_OPTIONS=""
> BR2_ENABLE_LOCALE=y
> BR2_ENABLE_LOCALE_PURGE=y
> BR2_ENABLE_LOCALE_WHITELIST="C en_US"
> BR2_GENERATE_LOCALE="en_US.UTF-8 en_US.ISO-8859-1"
> $ ./locale -a   # with  $(STAGING_DIR)/usr/bin/locale
> C
> en_US.iso88591
> en_US.utf8
> POSIX
> $ file /usr/lib/locale/locale-archive
> /usr/lib/locale/locale-archive: locale archive 26 strings
> 
> --
> Regards
> Einar J?n
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-02-05 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 17:23 [Buildroot] [Question] Glibc 2.27+ build and localedef Einar Jón
2019-02-05 17:33 ` Peter Seiderer [this message]
2019-02-06 13:38   ` Einar Jón

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=20190205183306.0a563445@gmx.net \
    --to=ps.report@gmx.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