Openembedded Core Discussions
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: openembedded-core@lists.openembedded.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] bitbake.conf: add "xz" to HOSTTOOLS
Date: Tue, 16 May 2023 20:30:07 +0200	[thread overview]
Message-ID: <20230516183009.1874105-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230516183009.1874105-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

xz is necessary to extract the uninative binary shims

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 meta/conf/bitbake.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index afd9e2f552..2a6aefc01a 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -529,7 +529,7 @@ HOSTTOOLS += " \
     python3 pzstd ranlib readelf readlink realpath rm rmdir rpcgen sed seq sh \
     sha1sum sha224sum sha256sum sha384sum sha512sum \
     sleep sort split stat strings strip tail tar tee test touch tr true uname \
-    uniq wc wget which xargs zstd \
+    uniq wc wget which xargs xz zstd \
 "
 
 # Tools needed to run testimage runtime image testing
-- 
2.34.1



  reply	other threads:[~2023-05-16 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 18:30 [PATCH 1/3] alsa-lib: upgrade 1.2.8 -> 1.2.9 michael.opdenacker
2023-05-16 18:30 ` michael.opdenacker [this message]
2023-05-16 18:30 ` [PATCH 2/3] alsa-ucm-conf: " michael.opdenacker
2023-05-16 18:30 ` [PATCH 3/3] alsa-utils: " michael.opdenacker
     [not found] ` <175FB334169DDB45.20583@lists.openembedded.org>
2023-05-16 18:35   ` [OE-core] [PATCH] bitbake.conf: add "xz" to HOSTTOOLS Michael Opdenacker
  -- strict thread matches above, loose matches on Subject: below --
2023-05-03  9:52 michael.opdenacker
2017-11-16  9:16 [PATCH] bitbake.conf: add 'xz' " André Draszik
2017-11-16 18:52 ` Khem Raj
2017-11-17  9:09   ` André Draszik

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=20230516183009.1874105-2-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=openembedded-core@lists.openembedded.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