From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: [meta-rockchip][PATCH] systemd: repart requires fdisk explicitly
Date: Tue, 22 Jul 2025 09:58:29 -0400 [thread overview]
Message-ID: <20250722135829.25568-1-twoerner@gmail.com> (raw)
According to [1], upstream meson's default configuration policy defaulted
to "auto", meaning that it would search as far and wide as it could
to find things like libraries and header files when deciding which
options to enable during configuration. Apparently that is no longer the
case, therefore new PACKAGECONFIG options have been added to systemd to
explicitly ask for some features.
systemd's repart mechanism needs fdisk, which was probably being found and
used implicitly before, but now needs to be enabled explicitly.
[1] oe-core: 4ec67113e1e7 ("systemd: add libblkid and libfdisk PACKAGECONFIG options")
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
.../rk-rauc-demo/recipes-core/systemd/systemd_%.bbappend | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dynamic-layers/rk-rauc-demo/recipes-core/systemd/systemd_%.bbappend b/dynamic-layers/rk-rauc-demo/recipes-core/systemd/systemd_%.bbappend
index cf6c188277db..ee4134d2e64d 100644
--- a/dynamic-layers/rk-rauc-demo/recipes-core/systemd/systemd_%.bbappend
+++ b/dynamic-layers/rk-rauc-demo/recipes-core/systemd/systemd_%.bbappend
@@ -1,3 +1,3 @@
inherit rk-rauc-demo-features-check
-PACKAGECONFIG:append:rk-rauc-demo = " repart openssl"
+PACKAGECONFIG:append:rk-rauc-demo = " repart openssl fdisk"
--
2.44.0.501.g19981daefd7c
next reply other threads:[~2025-07-22 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 13:58 Trevor Woerner [this message]
2025-07-22 14:07 ` [yocto-patches] [meta-rockchip][PATCH] systemd: repart requires fdisk explicitly Quentin Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250722135829.25568-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=yocto-patches@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.