Re: [OE-core] C.UTF-8 in glibc

2023-01-03 Thread Alexandre Belloni via lists.openembedded.org
On 02/01/2023 16:40:20+, Alex Kiernan wrote: > On Mon, Jan 2, 2023 at 4:28 PM Richard Purdie > wrote: > > > > On Sun, 2023-01-01 at 18:32 +, Alex Kiernan wrote: > > > glibc got an official C.UTF-8 in 2.35, but we don't appear to install > > > it by default... if I add "c" to IMAGE_LINGUAS

Re: [OE-core] C.UTF-8 in glibc

2023-01-02 Thread Alex Kiernan
On Mon, Jan 2, 2023 at 4:28 PM Richard Purdie wrote: > > On Sun, 2023-01-01 at 18:32 +, Alex Kiernan wrote: > > glibc got an official C.UTF-8 in 2.35, but we don't appear to install > > it by default... if I add "c" to IMAGE_LINGUAS then it gets installed, > > but it feels like this ought to b

Re: [OE-core] C.UTF-8 in glibc

2023-01-02 Thread Richard Purdie
On Sun, 2023-01-01 at 18:32 +, Alex Kiernan wrote: > glibc got an official C.UTF-8 in 2.35, but we don't appear to install > it by default... if I add "c" to IMAGE_LINGUAS then it gets installed, > but it feels like this ought to be default? Or even stronger and have > it separate from IMAGE_LI

[OE-core] C.UTF-8 in glibc

2023-01-01 Thread Alex Kiernan
glibc got an official C.UTF-8 in 2.35, but we don't appear to install it by default... if I add "c" to IMAGE_LINGUAS then it gets installed, but it feels like this ought to be default? Or even stronger and have it separate from IMAGE_LINGUAS so even if that's set to "" you still get it? I tripped