From: Khem Raj <raj.khem@gmail.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] bitbake.conf: change localedir
Date: Thu, 11 Aug 2016 12:47:54 -0700 [thread overview]
Message-ID: <F7382BD1-F606-47F7-9EF2-7F347F9D06D7@gmail.com> (raw)
In-Reply-To: <6cac214c-b73f-af4d-655f-f911788cdc3e@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
> On Aug 11, 2016, at 10:11 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
>
> On 8/11/16 11:26 AM, Burton, Ross wrote:
>>
>> On 8 August 2016 at 07:04, Chen Qi <Qi.Chen@windriver.com
>> <mailto:Qi.Chen@windriver.com>> wrote:
>>
>> Previously, localedir is set to "${libdir}/locale". This would result
>> in locale database installed in '/usr/lib64/locale' in some multilib case.
>> For example, if we build out a multilib x86-64 self-hosted image and we try
>> to build projects on this host, things broke and the following error appears.
>>
>> Please use a locale setting which supports utf-8.
>> Python can't change the filesystem locale after loading so we need a utf-8
>> when python starts or things won't work.
>>
>> This is because '/usr/lib/locale' is the default one. And actually the
>> nativesdk-glibc is now set to use '/usr/lib/locale'.
>>
>>
>> This is irrelevant as nativesdk-glibc is configured to read the *hosts* locale
>> directory.
>>
>>
>> Thus, we change the setting of 'localedir' to '${nonarch_libdir}/locale' to
>> fix the above problem.
>>
>>
>> I see two issues here:
>> 1) should binary locales be considered shared in multilib environments? (libdir
>> vs nonarch_libdir)
>> 2) what packages are not respecting this variable and hard-coding /usr/lib/locale?
>>
>> I'm guessing WR think yes to (1), and is the glibc patch you also sent the
>> fundamental fix to (2)?
>
> Binary locales have an endian and alignment setting to them. If a platform
> supports both big and little endian, this common locale would not work. (That
> is extremely rare....) Also if a platform supports different alignments in
> different libraries that could cause an impact as well. (This is also extremely
> unlikely.)
Are there any practical existing usecases ?
>
> The not-binary locales have no such issues BTW.
>
> --Mark
>
>> Ross
>>
>>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-08-11 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 6:04 [PATCH 0/1] bitbake.conf: change localedir Chen Qi
2016-08-08 6:04 ` [PATCH 1/1] " Chen Qi
2016-08-10 5:49 ` [PATCH] glibc: apply complocaledir while localedir changed Hongxu Jia
2016-08-10 5:55 ` Hongxu Jia
2016-08-10 7:31 ` [PATCH V2] " Hongxu Jia
2016-08-10 8:12 ` [PATCH V3] " Hongxu Jia
2016-08-11 16:26 ` [PATCH 1/1] bitbake.conf: change localedir Burton, Ross
2016-08-11 17:11 ` Mark Hatle
2016-08-11 19:14 ` Burton, Ross
2016-08-11 19:32 ` Mark Hatle
2016-08-11 19:47 ` Khem Raj [this message]
2016-08-12 13:50 ` Mark Hatle
2016-08-12 14:30 ` Radzykewycz, T (Radzy)
2016-08-12 3:28 ` ChenQi
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=F7382BD1-F606-47F7-9EF2-7F347F9D06D7@gmail.com \
--to=raj.khem@gmail.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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