Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Shirokov <shirokovalexs@gmail.com>
To: buildroot@buildroot.org
Cc: Alexander Shirokov <shirokovalexs@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/zellij: drop explicit architecture dependencies
Date: Wed, 11 Nov 2026 18:30:53 +0100	[thread overview]
Message-ID: <20261111173143.6336-1-shirokovalexs@gmail.com> (raw)

The strict architecture limitation was caused by the cranelift code
generator, which is part of wasmtime.

Zellij 0.44.0 migrated from wasmtime to wasmi [1], so cranelift is no
longer used. This allows relaxing the architecture dependencies and
building the package on more architectures.

However, zellij unconditionally uses AtomicU64, so add a dependency on
BR2_PACKAGE_HOST_RUSTC_TARGET_HAS_ATOMIC_U64.

Tested with test-pkg, which shows that the package can now be built for
more targets:

Before:
  32 builds, 26 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed

After:
  32 builds, 20 skipped, 0 build failed, 0 legal-info failed, 0 show-info failed

[1] https://github.com/zellij-org/zellij/pull/4449

Signed-off-by: Alexander Shirokov <shirokovalexs@gmail.com>
---
 package/zellij/Config.in | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/package/zellij/Config.in b/package/zellij/Config.in
index 7de6074435..97408f5f84 100644
--- a/package/zellij/Config.in
+++ b/package/zellij/Config.in
@@ -1,10 +1,8 @@
 config BR2_PACKAGE_ZELLIJ
 	bool "zellij"
-	# Zellij uses the cranelift crate which has architecure
-	# dependencies. Specify them explicitly. See details here:
-	# https://docs.rs/cranelift-codegen/0.122.0/cranelift_codegen/
-	depends on BR2_x86_64 || BR2_x86_i686 || BR2_aarch64
 	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
+	# zellij unconditionally uses AtomicU64
+	depends on BR2_PACKAGE_HOST_RUSTC_TARGET_HAS_ATOMIC_U64
 	select BR2_PACKAGE_HOST_RUSTC
 	help
 	  An advanced terminal multiplexer with batteries included.
-- 
2.56.0

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

                 reply	other threads:[~2026-11-11 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261111173143.6336-1-shirokovalexs@gmail.com \
    --to=shirokovalexs@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