On Mon, Feb 19, 2018 at 12:06 PM, Burton, Ross <ross.bur...@intel.com> wrote:
> Hi Khem,
>
> Sigh, sorry, should have realised.  So locale-archives are not compatible
> between glibc releases?  Good to know, I guess.
>

they are not and its recommended that static binaries be relinked.  I
am not sure
if our usecase is a supported one either

> Ross
>
> On 18 February 2018 at 07:58, Khem Raj <raj.k...@gmail.com> wrote:
>>
>> Wanted to send update on this issue
>>
>> I got to bottom of this issue and Ross you should have known it :)
>>
>> https://patchwork.openembedded.org/patch/127105/
>>
>> introduced an optimization into nativesdk glibc to let it ride on
>> localedate from SDK host. This has now broken in glibc with
>>
>>
>> https://github.com/kraj/glibc/commit/95cb863a1ef7760a11272bbd7ba5fe62dc41be54
>>
>> it is recommended for static programs to be relinked if using glibc 2.27
>> our case is also similar mismatch of libc version and localedata just in
>> opposite direction where we are trying to read old data with new glibc
>> instead.
>>
>> I have initiated a discussion within glibc community on it to explore what
>> options we have, but be prepared to ship full localedata in worst case with
>> glibc 2.27,  this might be the worst case option if no alternative is found.
>>
>> Thank you
>> -Khem
>>
>> On 2/15/18 4:12 AM, Burton, Ross wrote:
>>>
>>> Yes, that's it.
>>>
>>> Ross
>>>
>>> On 12 February 2018 at 07:32, Khem Raj <raj.k...@gmail.com
>>> <mailto:raj.k...@gmail.com>> wrote:
>>>
>>>     On Sat, Feb 3, 2018 at 2:21 AM, Burton, Ross <ross.bur...@intel.com
>>>     <mailto:ross.bur...@intel.com>> wrote:
>>>     > Getting there: https://autobuilder.yocto.io/tgrid
>>> <https://autobuilder.yocto.io/tgrid>
>>>     >
>>>     > Just two actual problems:
>>>     > - The non-gplv3 build failed as the make fix needs to be backported
>>> to
>>>     > meta-gplv2
>>>     > - The eSDK selftests all failed with en_US.UTF-8 problems, the new
>>> glibc
>>>     > shouldn't be causing a problem with uninative so this is
>>> interesting, maybe
>>>     > the new one is behaving slightly differently.  Should be easy to
>>> replicate.
>>>     > The same problem caused selftest to fail.
>>>     >
>>>
>>>     is the UTF error like this one
>>>     https://gist.github.com/25a84d23618824f0e5e6857a960eaca4
>>>     <https://gist.github.com/25a84d23618824f0e5e6857a960eaca4>
>>>
>>>      > Ross
>>>
>>>
>
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to