guix_mirror_bot pushed a commit to branch rust-team
in repository guix.
commit 9ce2a0c8cec0e162ff576b9a329625539a1597e2
Author: Efraim Flashner <[email protected]>
AuthorDate: Sun Nov 8 16:55:14 2026 +0200
build-system/cargo: Adjust RUSTFLAGS when building for wasm targets.
* guix/build/cargo-build-system.scm (configure): Don't add '--cap-lints
allow' to RUSTFLAGS when building for wasm targets.
---
guix/build/cargo-build-system.scm | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/guix/build/cargo-build-system.scm
b/guix/build/cargo-build-system.scm
index 9a82fca85fe..17efc7f0448 100644
--- a/guix/build/cargo-build-system.scm
+++ b/guix/build/cargo-build-system.scm
@@ -269,8 +269,10 @@ directory = '" vendor-dir "'\n") port)
;; into stricter lints (e.g. #![deny(warnings)]) during their own builds
;; but we don't want any build failures that could be caused later by
;; upgrading the compiler for example.
- (setenv "RUSTFLAGS" (string-append (or (getenv "RUSTFLAGS") "")
- " --cap-lints allow"))
+ ;; TODO: Is this the correct behavior for wasm targets?
+ (unless (string-contains (or target "") "wasm")
+ (setenv "RUSTFLAGS" (string-append (or (getenv "RUSTFLAGS") "")
+ " --cap-lints allow")))
(if (assoc-ref inputs "cross-gcc")
(begin