This upgrade failed on some of my hosts, and after checking what they had in common, seems it succeeded on systems which use EFI (for me, arm64, ia64, loong) and failed on systems which do not (everything else). Some sample logs attached. ninja -v -j1 -l0 systemd-tmpfiles man/tmpfiles.d.5 man/systemd-tmpfiles.8 tmpfiles.d/etc.conf tmpfiles.d/static-nodes-permissions.conf tmpfiles.d/var.conf udevadm systemd-hwdb ata_id cdrom_id dmi_memory_id fido_id iocost mtd_probe scsi_id v4l_id src/udev/udev.pc man/udev.conf.5 man/systemd.link.5 man/hwdb.7 man/udev.7 man/systemd-hwdb.8 man/systemd-udevd.service.8 man/udevadm.8 man/libudev.3 man/udev_device_get_syspath.3 man/udev_device_has_tag.3 man/udev_device_new_from_syspath.3 man/udev_enumerate_add_match_subsystem.3 man/udev_enumerate_new.3 man/udev_enumerate_scan_devices.3 man/udev_list_entry.3 man/udev_monitor_filter_update.3 man/udev_monitor_new_from_netlink.3 man/udev_monitor_receive_device.3 man/udev_new.3 hwdb.d/60-autosuspend-chromiumos.hwdb rules.d/50-udev-default.rules rules.d/60-persistent-storage.rules rules.d/64-btrfs.rules rules.d/99-systemd.rules libudev src/libudev/libudev.pc ninja: error: unknown target 'dmi_memory_id'
Created attachment 895395 [details] build.log and emerge --info (ppc64le)
Created attachment 895396 [details] build.log and emerge --info (sparc)
Created attachment 895397 [details] build.log and emerge --info (mips)
Created attachment 895398 [details] build.log and emerge --info (alpha)
Created attachment 895399 [details] build.log and emerge --info (riscv)
Created attachment 895400 [details] build.log and emerge --info (hppa)
It looks like there is a list of supported arches in meson.build. https://github.com/systemd/systemd/blob/v255/meson.build#L1453 > dmi_arches = ['x86', 'x86_64', 'aarch64', 'arm', 'ia64', 'loongarch64', 'mips']
(In reply to Mike Gilbert from comment #7) > It looks like there is a list of supported arches in meson.build. > > https://github.com/systemd/systemd/blob/v255/meson.build#L1453 > > > dmi_arches = ['x86', 'x86_64', 'aarch64', 'arm', 'ia64', 'loongarch64', 'mips'] Interesting, I don't really understand the point of doing this on specific arches only. Several of those can boot with or without EFI, at least one that can boot EFI (riscv) is missing, mips fails anyway (likely needs "mips64" instead of just "mips")...what is the point here?
I'm not sure. The list originates with this PR, without much explanation given. https://github.com/systemd/systemd/pull/18001
OK, want me to file upstream? What should we do in the meantime? This is completely broken on many arches.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7702b49add12ca5b5f6508bc5416f2a780ade761 commit 7702b49add12ca5b5f6508bc5416f2a780ade761 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2024-06-08 17:25:59 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2024-06-08 17:25:59 +0000 sys-apps/systemd-utils: fix build on arches without DMI At least according to systemd upstream. Closes: https://bugs.gentoo.org/933834 Signed-off-by: Mike Gilbert <floppym@gentoo.org> .../systemd-utils/systemd-utils-255.7-r1.ebuild | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-)
Can you adjust the mips CHOST check to be mips-*, since upstream incorrectly accounts for CHOST starting with mips64
(In reply to matoro from comment #10) If you would like to look into this upstream, that would be great. In the meantime, I added some logic to the ebuild to avoid build failure.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b3613ab440c7f0cee9ee0a8f3f230085a3dc65b2 commit b3613ab440c7f0cee9ee0a8f3f230085a3dc65b2 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2024-06-08 17:32:38 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2024-06-08 17:34:08 +0000 sys-apps/systemd-utils: exclude mips64 in have_dmi Bug: https://bugs.gentoo.org/933834 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd-utils/systemd-utils-255.7-r1.ebuild | 2 ++ 1 file changed, 2 insertions(+)
