Re: eglibc configurability

[Mark Hatle <mark.hatle@windriver.com>]

On 2/7/11 11:57 AM, Gary Thomas wrote:
> On 02/07/2011 10:04 AM, Mark Hatle wrote:
>> On 2/7/11 10:57 AM, Richard Purdie wrote:
>>> On Mon, 2011-02-07 at 09:54 -0700, Gary Thomas wrote:
>>>> On 02/07/2011 09:29 AM, Mark Hatle wrote:
>>>>> Could you find the related init script and point me to the contents.  I don't
>>>>> see any initscripts in the eglibc integration.  The only thing I see is a switch
>>>>> in the locale generation between on target, on host and via QEMU.  I'm wondering
>>>>> if maybe this is being triggered?
>>>>
>>>> This could be what I'm seeing.  I have ENABLE_BINARY_LOCALE_GENERATION disabled
>>>> in my local.conf (I had troubles with QEMU-ARM on Fedora in the past and this
>>>> was the way around it).  It looks like that may be pushing the locale compilation
>>>> to the target.
>>>
>>> Correct. The locales have to be generated somewhere!
>>>
>>> You turned them off on the build machine so they run on the target. All
>>> is functioning as it should.
>>>
>>> FWIW, cross locale gen doesn't use qemu now and is a lot faster so
>>> perhaps you could turn it back on ;-).
>>
>> Just to be clear, I'm running builds on machines where QEMU is unhappy (and I've
>> disabled the QEMU check...)  I have locales being generated and they are working
>> fine in the testing I have done with them.
>>
>> This is using eglibc and the default conf file configuration setting.
> 
> I enabled ENABLE_BINARY_LOCALE_GENERATION and now the locale
> generation is being done at build time - hurray :-)  Boot time
> is much improved.
> 
> Now to figure out how to control the ones that are installed.

The value is "IMAGE_LINGUAS".  It defaults to "en-us en-gb".

(default is located in meta/conf/distro/poky.conf.. but you should override this
in your build/conf/local.conf)

--Mark

> Thanks
>