From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: uvv.mail@gmail.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v4] systemd: Build the systemctl executable
Date: Mon, 10 Feb 2025 10:14:25 +0200 [thread overview]
Message-ID: <Z6m1YdpNtlNbMekB@nuoska> (raw)
In-Reply-To: <1949d535-d442-476f-85b6-55b018c4057c@gmail.com>
Hi,
On Mon, Feb 10, 2025 at 09:07:57AM +0100, Vyacheslav Yurkov via lists.openembedded.org wrote:
> On 08.02.2025 19:34, Richard Purdie wrote:
> > On Fri, 2025-02-07 at 08:10 +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������ |� 23 +-
> > > �...-meson-add-install-tag-for-systemctl.patch |� 25 ++
> > > �...2-meson-Bypass-certain-config-checks.patch |� 64 +++
> > > �.../systemd/systemd-systemctl/systemctl������ | 366 ------------------
> > > �4 files changed, 100 insertions(+), 378 deletions(-)
> > > �create mode 100644 meta/recipes-core/systemd/systemd-systemctl/0001-meson-add-install-tag-for-systemctl.patch
> > > �create mode 100644 meta/recipes-core/systemd/systemd-systemctl/0002-meson-Bypass-certain-config-checks.patch
> > > �delete mode 100755 meta/recipes-core/systemd/systemd-systemctl/systemctl
> > Unfortunately this showed circular dependency errors in testing:
> >
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/76/builds/933
> >
> > Cheers,
> >
> > Richard
>
> I believe the failure comes from util-linux. Any idea how to "inherit"
> conditionally only for target builds? (without creating a separate native
> recipe).
Set a variable conditionally and use that with "inherit".
FOO = ""
FOO:class-target = "bar"
inherit ${FOO}
Cheers,
-Mikko
next prev parent reply other threads:[~2025-02-10 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 7:10 [PATCH v4] systemd: Build the systemctl executable uvv.mail
2025-02-08 18:34 ` [OE-core] " Richard Purdie
2025-02-10 8:07 ` Vyacheslav Yurkov
2025-02-10 8:14 ` Mikko Rapeli [this message]
2025-02-10 17:09 ` Quentin Schulz
[not found] <1821DB8546489F1A.752@lists.openembedded.org>
2025-02-07 7:12 ` 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=Z6m1YdpNtlNbMekB@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox