From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Stefan Agner <stefan@agner.ch>
Cc: meta-virtualization@lists.yoctoproject.org,
Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [meta-virtualization][PATCH v2] conmon: compile with journald support if systemd is enabled
Date: Wed, 29 Jan 2020 10:39:01 -0500 [thread overview]
Message-ID: <20200129153857.GA54261@gmail.com> (raw)
In-Reply-To: <20200127214854.29367-1-stefan@agner.ch>
merged.
Bruce
In message: [meta-virtualization][PATCH v2] conmon: compile with journald support if systemd is enabled
on 27/01/2020 Stefan Agner wrote:
> From: Stefan Agner <stefan.agner@toradex.com>
>
> Currently conman is compiled without journald support which leads to
> this error message when trying to use it (e.g. --log-driver=journald
> with podman):
> [conmon:e] Include journald in compilation path to log to systemd journal
>
> Make sure to build with journald backend compiled-in when systemd is in
> distro features by adding systemd to DEPENDS (through PACKAGECONFIG).
>
> Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
> ---
> recipes-containers/conmon/conmon_2.0.9.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/recipes-containers/conmon/conmon_2.0.9.bb b/recipes-containers/conmon/conmon_2.0.9.bb
> index fc76f15..af7847b 100644
> --- a/recipes-containers/conmon/conmon_2.0.9.bb
> +++ b/recipes-containers/conmon/conmon_2.0.9.bb
> @@ -20,6 +20,9 @@ inherit pkgconfig
>
> EXTRA_OEMAKE = "PREFIX=${prefix} BINDIR=${bindir} LIBEXECDIR=${libexecdir}"
>
> +PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', d)}"
> +PACKAGECONFIG[systemd] = ",,systemd"
> +
> do_install() {
> oe_runmake 'DESTDIR=${D}' install
> }
> --
> 2.17.1
>
>
prev parent reply other threads:[~2020-01-29 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 21:48 [meta-virtualization][PATCH v2] conmon: compile with journald support if systemd is enabled Stefan Agner
2020-01-29 15:39 ` Bruce Ashfield [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=20200129153857.GA54261@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=stefan.agner@toradex.com \
--cc=stefan@agner.ch \
/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.