From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 2/2] rauc: select HOST_MESON
Date: Wed, 16 Aug 2023 11:23:38 +0200 [thread overview]
Message-ID: <20230816092338.5fsfggojlp4zblxf@pengutronix.de> (raw)
In-Reply-To: <20230813194844.1961020-2-rhi@pengutronix.de>
On Sun, Aug 13, 2023 at 09:48:44PM +0200, Roland Hieber wrote:
> RAUC has been using meson since commit 6e72460fe79714249b81 (2023-06-30,
> Enrico Jorns: "rauc: migrate to meson"), but now PTXdist warns about the
> missing HOST_MESON dependency in the prepare stage.
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> v2: no change in this version
> v1: https://lore.ptxdist.org/ptxdist/20230810110256.2242386-2-rhi@pengutronix.de
… yes, the rebased patch still applies, but now there are two HOST_MESON
selects in this file. Nothing to do here, please disregard. First patch
still applies.
- Roland
>
> rules/rauc.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/rules/rauc.in b/rules/rauc.in
> index e67f5131c615..94a7859d89f5 100644
> --- a/rules/rauc.in
> +++ b/rules/rauc.in
> @@ -8,6 +8,7 @@ menuconfig RAUC
> select GLIB
> select GLIB_LIBMOUNT
> select HOST_GLIB
> + select HOST_MESON
> select CODE_SIGNING
> select BUSYBOX_FEATURE_TAR_LONG_OPTIONS if BUSYBOX_TAR
> select BUSYBOX_FEATURE_TAR_AUTODETECT if BUSYBOX_TAR
> --
> 2.39.2
>
>
>
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-08-16 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 19:48 [ptxdist] [PATCH v2 1/2] rauc: fix license and add license files checksums Roland Hieber
2023-08-13 19:48 ` [ptxdist] [PATCH v2 2/2] rauc: select HOST_MESON Roland Hieber
2023-08-16 9:23 ` Roland Hieber [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=20230816092338.5fsfggojlp4zblxf@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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