Re: [OE-core] [RFC] gettext, gettext-native-minimal: upgrade 0.23.1 -> 0.26

[Gyorgy Sarvari <skandigraun@gmail.com>]

On 9/1/25 10:21, Mathieu Dubois-Briand wrote:
> On Sat Aug 30, 2025 at 10:58 PM CEST, Gyorgy Sarvari via lists.openembedded.org wrote:
>> On 8/30/25 22:55, Gyorgy Sarvari via lists.openembedded.org wrote:
>> In principle I think that it's about as I can make it on my own (sans AB
>> failures[1]), but there would be a few question marks on my end:
>>
>> 1. If you have a better idea for relevant Makefile.in.in heurestics in
>> autotools.bbclass, I'm listening
>> 2. I *think* that the Makevars concatenation makes actual sense, and the
>> build success is not only an accident - but I'm not 100% sure if that's
>> the best way to handle this. If you know gettext, I'd like to hear your
>> opinion. (This was inspired by gettextize's behavior. Upon running it,
>> it copies the Makevars.template with default values in the po folder,
>> and asks you to set up all the variables from it in your Makevars file)
>>
>> [1]: I did build recipes and multiple images successfully, but not
>> "bitbake world" on multiple configs
> Hi Gyorgy,
>
> I took a bit of time to launch a build on the autobuilder. It looks like
> this is breaking build of several components: glib, e2fsprogs, iso-codes
> and so on. I saw two types of errors so far:
> - undefined symbol: getfilecon
> - missing files: t-ca.gmo, t-bg.gmo... I'm not sure where this comes
>   from.
>
> ERROR: glib-2.0-initial-1_2.84.4-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/x86-64-v3-poky-linux/glib-2.0-initial/2.84.4/temp/run.do_compile.3022462' failed with exit code 127
> ...
> | /srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/x86-64-v3-poky-linux/glib-2.0-initial/2.84.4/recipe-sysroot-native/usr/bin/msgfmt: symbol lookup error: /srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/x86-64-v3-poky-linux/glib-2.0-initial/2.84.4/recipe-sysroot-native/usr/bin/../lib/libgettextlib-0.26.so: undefined symbol: getfilecon
>
> ERROR: e2fsprogs-1.47.3-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/x86-64-v3-poky-linux/e2fsprogs/1.47.3/temp/run.do_compile.3185668' failed with exit code 1
> ...
> | mv: cannot stat 't-ca.gmo': No such file or directory
>
> ERROR: iso-codes-4.18.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/all-poky-linux/iso-codes/4.18.0/temp/run.do_compile.3458421' failed with exit code 1
> ...
> | /srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/all-poky-linux/iso-codes/4.18.0/recipe-sysroot-native/usr/bin/msgfmt: symbol lookup error: /srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/all-poky-linux/iso-codes/4.18.0/recipe-sysroot-native/usr/bin/../lib/libgettextlib-0.26.so: undefined symbol: getfilecon
>
> ERROR: Logfile of failure stored in: /srv/pokybuild/yocto-worker/no-x11/build/build/tmp/work/x86-64-v3-poky-linux/psmisc/23.7/temp/log.do_compile.3498395
> ...
> | mv: cannot stat 't-bg.gmo': No such file or directory
>
> You can get all logs here:
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/2220
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/2285
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2330
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/2308
>
> We can have more failure logs in all a-full subbuilders, but they all
> look the same as far as I can see.
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2299

Thanks for taking it for a spin.

This is just a keep-alive ping from my end for now.
It is not being ignored, but reproduction is doesn't seem to be
straightforward - will report back.

> Thanks,
> Mathieu
>