From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/3] tools build: Add Rust library build infrastructure and zlib-rs feature test
Date: Fri, 30 Oct 2026 20:44:47 +0000 [thread overview]
Message-ID: <sashiko-outbox-191491@kernel.org> (raw)
In-Reply-To: <20261030202710.3863806-2-irogers@google.com>
> Add shared Rust library build and feature detection support across tools/
> and implement the zlib-rs feature check:
>
> - Add tools/build/Makefile.rust with rules to resolve Rust library C
> compiler and linker flags via %-cflags and %-libs targets.
> - Support resolving zlib-rs via LIBZ_RS_DIR, pkg-config
> (libz-rs-sys-cdylib, zlib-rs, z_rs), or building libz_rs.a into
> $(OUTPUT)libz_rs/ from the system Cargo registry
> (/usr/share/cargo/registry) using offline Cargo (cargo metadata and
> cargo build --offline).
> - Add tools/build/feature/test-zlib-rs.c verifying ZLIB_VER_SUBREVISION
> == 15 (0xf) and linking against inflateInit().
> - Add RUST_TARGET_FLAGS_<arch> cross-compilation triples and the
> feature_rust_lib helper macro to tools/scripts/Makefile.include.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261030202710.3863806-1-irogers@google.com?part=1
next prev parent reply other threads:[~2026-10-30 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 20:27 [RFC PATCH v2 0/3] tools: Add Rust library build infrastructure and prefer zlib-rs Ian Rogers
2026-10-30 20:27 ` [RFC PATCH v2 1/3] tools build: Add Rust library build infrastructure and zlib-rs feature test Ian Rogers
2026-10-30 20:44 ` sashiko-bot [this message]
2026-10-30 20:27 ` [RFC PATCH v2 2/3] perf build: Prefer zlib-rs over zlib when available Ian Rogers
2026-10-30 20:46 ` sashiko-bot
2026-10-30 20:27 ` [RFC PATCH v2 3/3] bpftool: " Ian Rogers
2026-10-30 20:39 ` sashiko-bot
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=sashiko-outbox-191491@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 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.