From: <kai.kang@windriver.com>
To: <meta-virtualization@lists.yoctoproject.org>
Subject: [PATCH v2 2/4] docker-compose: not compatible with mips
Date: Thu, 14 Sep 2023 15:52:58 +0800 [thread overview]
Message-ID: <20230914075300.773380-3-kai.kang@windriver.com> (raw)
In-Reply-To: <20230914075300.773380-1-kai.kang@windriver.com>
From: Kai Kang <kai.kang@windriver.com>
docker-compose rdepends on docker which is not compatible with mips.
So set COMPATIBLE_HOST for docker-compose accordingly.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
recipes-containers/docker-compose/docker-compose_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-containers/docker-compose/docker-compose_git.bb b/recipes-containers/docker-compose/docker-compose_git.bb
index ca50abad..274fb520 100644
--- a/recipes-containers/docker-compose/docker-compose_git.bb
+++ b/recipes-containers/docker-compose/docker-compose_git.bb
@@ -32,6 +32,8 @@ COMPOSE_PKG = "github.com/docker/compose/v2"
inherit go goarch
inherit pkgconfig
+COMPATIBLE_HOST = "^(?!mips).*"
+
do_configure[noexec] = "1"
PACKAGECONFIG ?= ""
--
2.34.1
next prev parent reply other threads:[~2023-09-14 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:52 [PATCH v2 0/4] Update COMPATIBLE_HOST kai.kang
2023-09-14 7:52 ` [PATCH v2 1/4] packagegroup-container: not compatible with mips and riscv kai.kang
2023-09-14 7:52 ` kai.kang [this message]
2023-09-14 7:52 ` [PATCH v2 3/4] packagegroup-kubernetes: set COMPATIBLE_HOST kai.kang
2023-09-14 7:53 ` [PATCH v2 4/4] k3s: not compatible with mips kai.kang
2023-09-15 17:31 ` [meta-virtualization] [PATCH v2 0/4] Update COMPATIBLE_HOST Bruce Ashfield
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=20230914075300.773380-3-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).