From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <peter.kjellerstedt@axis.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCHv5 1/2] systemd-systemctl-native: Install systemd-sysv-install
Date: Sun, 24 Aug 2025 08:37:15 +0200 [thread overview]
Message-ID: <DCAG899Q8S22.1OYPXIT6S98BJ@bootlin.com> (raw)
In-Reply-To: <AS8PR02MB10201B91F7032A65E7A8B98B5EF3DA@AS8PR02MB10201.eurprd02.prod.outlook.com>
On Fri Aug 22, 2025 at 8:29 PM CEST, Peter Kjellerstedt via lists.openembedded.org wrote:
>
> I figured it out. It failed when building from sstate because even if
> I fixed so that the path to systemd-sysv-install wasn’t hardcoded into
> systemctl, it was still hardcoded into the RPM scripts. :(
>
> I have sent updated versions of the patches that should not result in
> any hardcoded paths anywhere, and this time I have verified all
> combinations I could think of with and without sstate, and with and
> without sysvinit in DISTRO_FEATURES.
>
> //Peter
Hi Peter,
I confirm the build went well with the new version of your series.
Thanks!
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-08-24 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 13:42 [PATCHv5 1/2] systemd-systemctl-native: Install systemd-sysv-install Peter Kjellerstedt
2025-08-20 13:42 ` [PATCHv5 2/2] systemd.bbclass: Make systemd_postinst run as intended Peter Kjellerstedt
2025-08-21 6:38 ` [OE-core] [PATCHv5 1/2] systemd-systemctl-native: Install systemd-sysv-install Mathieu Dubois-Briand
2025-08-21 15:11 ` Peter Kjellerstedt
2025-08-21 19:19 ` Mathieu Dubois-Briand
2025-08-22 18:29 ` Peter Kjellerstedt
2025-08-24 6:37 ` Mathieu Dubois-Briand [this message]
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=DCAG899Q8S22.1OYPXIT6S98BJ@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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.