Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@buildroot.org
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: [Buildroot] [PATCH] package/libostree: select libarchive for s390x architecture
Date: Tue, 11 Oct 2022 08:26:47 +0200	[thread overview]
Message-ID: <20221011062647.741292-1-marcus.folkesson@gmail.com> (raw)

libarchive is needed when building for s390x.

Introduced in this patch:
c6a53ef6e8f9491633b0d494991f94c629791e1d s390x: use 'libarchive' to modify initrd in SE case

Fixes:
http://autobuild.buildroot.net/results/14cc164ab3005be9b3efde57b4bd914414e3acf0/

Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
---
 package/libostree/Config.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/libostree/Config.in b/package/libostree/Config.in
index 14ae4da4c8..a36e12ddde 100644
--- a/package/libostree/Config.in
+++ b/package/libostree/Config.in
@@ -7,6 +7,7 @@ config BR2_PACKAGE_LIBOSTREE
 	# doesn't build with musl due to lack of TEMP_FAILURE_RETRY()
 	depends on !BR2_TOOLCHAIN_USES_MUSL
 	select BR2_PACKAGE_E2FSPROGS
+    select BR2_PACKAGE_LIBARCHIVE if BR2_s390x
 	select BR2_PACKAGE_LIBGLIB2
 	select BR2_PACKAGE_LIBGPG_ERROR
 	select BR2_PACKAGE_LIBGPGME
-- 
2.37.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-10-11  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  6:26 Marcus Folkesson [this message]
2022-10-24  5:47 ` [Buildroot] [PATCH] package/libostree: select libarchive for s390x architecture Marcus Folkesson
2022-10-31 10:27 ` Thomas Petazzoni via buildroot

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=20221011062647.741292-1-marcus.folkesson@gmail.com \
    --to=marcus.folkesson@gmail.com \
    --cc=buildroot@buildroot.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