From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 68903@debbugs.gnu.org
Subject: [bug#68903] fix builds on !x86_64 and update to 1.0.34
Date: Fri, 02 Feb 2024 18:42:36 -0800 [thread overview]
Message-ID: <871q9u8e03.fsf@wireframe> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
The attached patch updates wabt to 1.0.34 and also disables tests on
non-x86_64 architectures.
Since the update to wabt 1.0.32 in commit
9d474e105977e46d1ffd9afe794d26882a66c7a0, tests were also enabled... but
it has failed to build architectures other than x86_64 ever since...
Because of this, diffoscope and reprotest have not been able to build,
as diffoscope has wabt in native-inputs.
Thanks to ulfvonbelow via #guix IRC for the simple suggestion of how to
disable tests!
Another option would be to selectively disable tests, though
historically there have been a number of relevent outstanding issues
related to tests on !x86_64, which might turn into a few rounds of
whack-a-mole every time wabt is updated:
https://github.com/WebAssembly/wabt/issues/1045
https://github.com/WebAssembly/wabt/issues/1044
https://github.com/WebAssembly/wabt/issues/2118
https://github.com/WebAssembly/wabt/issues/2240
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-gnu-wabt-Update-to-1.0.34.patch --]
[-- Type: text/x-diff, Size: 1545 bytes --]
From a378a8b7b23c2be9f8374d28fc1f89134a9fd272 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
Date: Fri, 2 Feb 2024 15:32:04 -0800
Subject: [PATCH] gnu: wabt: Update to 1.0.34.
* gnu/packages/web.scm (wabt): Update to 1.0.34.
[arguments]: Disable tests on !x86_64.
---
gnu/packages/web.scm | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
index 1a97dd8dec..1eefb1fde7 100644
--- a/gnu/packages/web.scm
+++ b/gnu/packages/web.scm
@@ -1638,7 +1638,7 @@ (define-public libwebsockets
(define-public wabt
(package
(name "wabt")
- (version "1.0.32")
+ (version "1.0.34")
(source
(origin
(method git-fetch)
@@ -1648,13 +1648,15 @@ (define-public wabt
(recursive? #true)))
(file-name (git-file-name name version))
(sha256
- (base32 "0m124r8v9c0hxiaa4iy7ch4ng8msnirbc2vb702gbdjhvgzyrcwh"))
+ (base32 "1vxvc34b7a7lkrmzdb5cjv0b54vhiyr33sy0i2ps5jrmg5rqqmia"))
(modules '((guix build utils)))
(snippet
'(delete-file-recursively "third_party/gtest/"))))
(build-system cmake-build-system)
(arguments
(list
+ ;; Tests on non-x86_64 architectures are not well supported upstream.
+ #:tests? (target-x86-64?)
#:test-target "run-tests"
#:configure-flags '(list "-DUSE_SYSTEM_GTEST=ON")
#:phases
base-commit: f45d05133472a9da13eae20ba4a676c696682c90
--
2.39.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2024-02-03 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 2:42 Vagrant Cascadian [this message]
2024-02-09 21:47 ` bug#68903: wabt: fix builds on !x86_64 and update to 1.0.34 Vagrant Cascadian
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=871q9u8e03.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=68903@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.