C.UTF-8 in glibc

C.UTF-8 in glibc

[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 over it because I was trying to get the ostree ptest suite
to pass and it ended up with a time formatting failing a test because
it wasn't running in C.UTF-8.

-- 
Alex Kiernan

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

[Richard Purdie]

On Sun, 2023-01-01 at 18:32 +0000, 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_LINGUAS so even if that's set to "" you still
> get it?
> 
> I tripped over it because I was trying to get the ostree ptest suite
> to pass and it ended up with a time formatting failing a test because
> it wasn't running in C.UTF-8.

Making it even stronger might be tricky given how our variables work
but we definitely should have that in the default locales list.

Cheers,

Richard

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

[Alex Kiernan]

On Mon, Jan 2, 2023 at 4:28 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Sun, 2023-01-01 at 18:32 +0000, 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_LINGUAS so even if that's set to "" you still
> > get it?
> >
> > I tripped over it because I was trying to get the ostree ptest suite
> > to pass and it ended up with a time formatting failing a test because
> > it wasn't running in C.UTF-8.
>
> Making it even stronger might be tricky given how our variables work
> but we definitely should have that in the default locales list.
>

My original thinking on trying to make it stronger was I expect you
really want this, but given everyone's managed so far without, I guess
if they need it now they can add it back in if they're overriding
IMAGE_LINGUAS.

Just thinking about this more, we can't specify it for musl, the
obvious way would be a glibc specific append, which would then mean
that setting IMAGE_LINGUAS = "" you still get it, which doesn't
immediately feel right (plus the general wish to avoid append in
core), which I guess means it needs something with more trickery...
I'll go play.

-- 
Alex Kiernan

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

[Alexandre Belloni]

On 02/01/2023 16:40:20+0000, Alex Kiernan wrote:
> On Mon, Jan 2, 2023 at 4:28 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Sun, 2023-01-01 at 18:32 +0000, 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_LINGUAS so even if that's set to "" you still
> > > get it?
> > >
> > > I tripped over it because I was trying to get the ostree ptest suite
> > > to pass and it ended up with a time formatting failing a test because
> > > it wasn't running in C.UTF-8.
> >
> > Making it even stronger might be tricky given how our variables work
> > but we definitely should have that in the default locales list.
> >
> 
> My original thinking on trying to make it stronger was I expect you
> really want this, but given everyone's managed so far without, I guess
> if they need it now they can add it back in if they're overriding
> IMAGE_LINGUAS.
> 
> Just thinking about this more, we can't specify it for musl, the
> obvious way would be a glibc specific append, which would then mean
> that setting IMAGE_LINGUAS = "" you still get it, which doesn't
> immediately feel right (plus the general wish to avoid append in
> core), which I guess means it needs something with more trickery...
> I'll go play.
> 

Maybe:

IMAGE_LINGUAS_C:libc-glibc = "c"
IMAGE_LINGUAS = "${IMAGE_LINGUAS_C}"

> -- 
> Alex Kiernan

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#175323): https://lists.openembedded.org/g/openembedded-core/message/175323
> Mute This Topic: https://lists.openembedded.org/mt/95993257/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com