Re: [OE-core][PATCH 2/2] systemd: upgrade from 257.8 to 258

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Tue Oct 14, 2025 at 2:15 PM CEST, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> 258 Release Changes:
> https://github.com/systemd/systemd/releases/tag/v258
>
> The 'runlevel', 'initctl', 'telinit' related contents are removed
> because they are offically removed in v258.
>
> Disable tests explicitly. This is because we're not installing any
> tests. There's no point building them out. And this puts extra burden
> on making things compile for musl.
>
> musl changes:
> 1. The -D__UAPI_DEF_ETHHDR=0 is removed from TARGET_CC_ARCH.
>    The __UAIP_DEF_ETHHDR is defined as 0 in netinet/if_ether.h in
>    musl. There's no need to explicitly define it in compiler
>    commandline. And such explicit definition will break the logic
>    of the header files in systemd, resulting in extra patches.
> 2. All patches are re-evaluated.
>    This version of systemd introduces big changes in header
>    files and other places. So the previous musl patches are
>    re-evaluated one by one. Those that are dropped are considered not
>    needed. A few new ones are added. There are some notable ones.
>    0012-do-not-disable-buffer-in-writing-files.patch is dropped because
>    there is not runtime error.
>    0016-Fix-the-segfault-for-glob-related-codes-and-define-d.patch is
>    added because this version of systemd uses strv_free to free gl_pathv
>    instead of relying on globfree provided by libc.
> 3. The 'struct ethhdr' re-definition error is solved in musl recipe.
>    If musl upstream does not accept the patches, we'll need to use
>    previous method and change quite a few files.
>    https://www.openwall.com/lists/musl/2025/09/30/1
>    https://www.openwall.com/lists/musl/2025/09/30/2
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---

Hi Chen,

I saw your message saying this is not ready to merge, but I already had
this in testing and got some warnings:

WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: Group clock has never been defined

https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/2560

They do appear while building with poky-altcfg distro, for all machines
and probably all images. It was confirmed here with core-image-minimal.

Can you investigate this before your next iteration?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com