From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: uvv.mail@gmail.com, Openembedded-core@lists.openembedded.org
Cc: Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: Re: [OE-core] [PATCH v5 1/2] systemd: Build the systemctl executable
Date: Wed, 19 Feb 2025 09:44:09 +0000 [thread overview]
Message-ID: <357c680fc29707fa3d6b9d934305acfb2df22c1f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250218115647.40502-1-uvv.mail@gmail.com>
On Tue, 2025-02-18 at 12:56 +0100, Vyacheslav Yurkov via
lists.openembedded.org wrote:
> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>
> Instead of the python re-implementation build the actual systemctl
> from
> the systemd source tree. The python script was used when systemd
> didn't
> provide an option to build individual executables. It is possible in
> the
> meantime, so instead of always adapting the script when there's a new
> functionality, we simply use upstream implementation.
>
> License-Update: Base recipe is used
>
> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
> ---
> .../systemd/systemd-systemctl-native.bb | 26 +-
> ...-meson-add-install-tag-for-systemctl.patch | 25 ++
> ...2-meson-Bypass-certain-config-checks.patch | 64 +++
> .../systemd/systemd-systemctl/systemctl | 376 ----------------
> --
>
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/1022
and many similar failures unfortunately. Did we get out of sync with
systemd versions?
I'm keen to have something like this recipe so thanks for working on
it.
Cheers,
Richard
next prev parent reply other threads:[~2025-02-19 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 11:56 [PATCH v5 1/2] systemd: Build the systemctl executable uvv.mail
2025-02-18 11:56 ` [PATCH v5 2/2] oeqa/selftest: Drop dependency on systemd-native uvv.mail
2025-02-18 12:09 ` Mikko Rapeli
2025-02-19 9:44 ` Richard Purdie [this message]
2025-02-19 10:02 ` [OE-core] [PATCH v5 1/2] systemd: Build the systemctl executable Mikko Rapeli
2025-02-19 10:14 ` Vyacheslav Yurkov
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=357c680fc29707fa3d6b9d934305acfb2df22c1f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=mikko.rapeli@linaro.org \
--cc=uvv.mail@gmail.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.