<div dir="ltr">Hi Khem,<div><br></div><div>Sigh, sorry, should have realised. So locale-archives are not compatible between glibc releases? Good to know, I guess.</div><div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 February 2018 at 07:58, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wanted to send update on this issue<br>
<br>
I got to bottom of this issue and Ross you should have known it :)<br>
<br>
<a href="https://patchwork.openembedded.org/patch/127105/" rel="noreferrer" target="_blank">https://patchwork.openembedded<wbr>.org/patch/127105/</a><br>
<br>
introduced an optimization into nativesdk glibc to let it ride on localedate from SDK host. This has now broken in glibc with<br>
<br>
<a href="https://github.com/kraj/glibc/commit/95cb863a1ef7760a11272bbd7ba5fe62dc41be54" rel="noreferrer" target="_blank">https://github.com/kraj/glibc/<wbr>commit/95cb863a1ef7760a11272bb<wbr>d7ba5fe62dc41be54</a><br>
<br>
it is recommended for static programs to be relinked if using glibc 2.27<br>
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.<br>
<br>
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.<br>
<br>
Thank you<br>
-Khem<span class=""><br>
<br>
On 2/15/18 4:12 AM, Burton, Ross wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Yes, that's it.<br>
<br>
Ross<br>
<br></span><span class="">
On 12 February 2018 at 07:32, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a> <mailto:<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>>> wrote:<br>
<br>
On Sat, Feb 3, 2018 at 2:21 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a><br></span>
<mailto:<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>><wbr>> wrote:<br>
> Getting there: <a href="https://autobuilder.yocto.io/tgrid" rel="noreferrer" target="_blank">https://autobuilder.yocto.io/t<wbr>grid</a> <<a href="https://autobuilder.yocto.io/tgrid" rel="noreferrer" target="_blank">https://autobuilder.yocto.io/<wbr>tgrid</a>><span class=""><br>
><br>
> Just two actual problems:<br>
> - The non-gplv3 build failed as the make fix needs to be backported to<br>
> meta-gplv2<br>
> - The eSDK selftests all failed with en_US.UTF-8 problems, the new glibc<br>
> shouldn't be causing a problem with uninative so this is interesting, maybe<br>
> the new one is behaving slightly differently. Should be easy to replicate.<br>
> The same problem caused selftest to fail.<br>
><br>
<br>
is the UTF error like this one<br>
<a href="https://gist.github.com/25a84d23618824f0e5e6857a960eaca4" rel="noreferrer" target="_blank">https://gist.github.com/25a84d<wbr>23618824f0e5e6857a960eaca4</a><br></span>
<<a href="https://gist.github.com/25a84d23618824f0e5e6857a960eaca4" rel="noreferrer" target="_blank">https://gist.github.com/25a84<wbr>d23618824f0e5e6857a960eaca4</a>><br>
<br>
> Ross<br>
<br>
<br>
</blockquote>
</blockquote></div><br></div>