From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: Alejandro Hernandez <alhe@linux.microsoft.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>,
"MacLeod, Randy" <Randy.MacLeod@windriver.com>,
"alejandro@enedino.org" <alejandro@enedino.org>
Subject: Re: [OE-core] [PATCH 0/5] rust: reproducibility fixes for arm build hosts
Date: Tue, 15 Sep 2026 16:10:15 +0000 [thread overview]
Message-ID: <1b9e30b7-6836-4ff7-a716-b7e87bf3d51e@windriver.com> (raw)
In-Reply-To: <b8a0599c-a7e4-44b5-b8c9-6a72d14a70fc@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 6844 bytes --]
On 9/15/2026 9:23 PM, Alejandro Hernandez wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hopefully these fix reproducibility issue when built from different hosts.
Unfortunately these go in a bit of a different way than my next version, so I
will wait for the result before sending to avoid confusion, but I'm fine with these
if they work, lets just add my sign off to the actual patches based off of mine
instead of the "Patch from Alejandro + OE link".
Thanks Alejandro. Your series did the hard part here, finding where the host details get into the
rust builds in the first place. Mine builds on that map.
On the contrib branch run the arm reproducible builders came back with the rust family gone
from the failing list, so it looks good so far. The real confirmation will be the autobuilder runs on
master-next once the series gets picked up there.
On the sign-off: your Signed-off-by is already inside the two carried patch files, but you are right that it is not in
the commit messages, so git log only shows mine.
In v2 I will add your Signed-off-by to those two commit messages and drop the "Patch from + link" wording,
together with whatever else the review brings up.
Thanks,
Sunil Dora
Cheers
Alejandro
On 9/15/2026 8:18 AM, Dora, Sunil Kumar via lists.openembedded.org<https://urldefense.com/v3/__http://lists.openembedded.org__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW77Ut4JIQ$> wrote:
From: Sunil Dora <sunilkumar.dora@windriver.com><mailto:sunilkumar.dora@windriver.com>
The reproducible selftest fails for rust on the arm workers
([YOCTO #16376]). This series fixes that.
rust: drop the cc object-name reproducibility patch
rust: hash cc object names relative to their source roots
The patch we carried trimmed the build path by matching the string
"rustc", and the shared-source rework broke that for one of the two
sets of sources cc compiles. The replacement strips the roots the
sources actually come from. The OUT_DIR part is proposed upstream as
https://github.com/rust-lang/cc-rs/pull/1902<https://urldefense.com/v3/__https://github.com/rust-lang/cc-rs/pull/1902__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW4fqdQsfQ$>.
The RUST_COMPILER_RT_ROOT part is specific to rust's own build
system, so it is not part of that pull request.
rust: keep the build host triple out of cargo unit metadata
From Alejandro Enedino Hernandez Samaniego's strict-version-hash
series, carried with his sign-off:
https://lists.openembedded.org/g/openembedded-core/topic/120939810<https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/topic/120939810__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW7uALNnJw$>
cargo mixes the "host:" line of "rustc -vV" into build script and
proc-macro metadata, and target crates inherit it.
Upstream report: https://github.com/rust-lang/cargo/issues/8140<https://urldefense.com/v3/__https://github.com/rust-lang/cargo/issues/8140__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW7EZ-2c1Q$>
rust: backport deterministic DocLinkResMap serialisation
Upstream commit f9d9939 by jprochazk and mejrs. It is in rust 1.99,
so this drops out at the next rust upgrade.
rust: sort hygiene data before it is encoded
Also from Alejandro's series. Upstream is fixing the same problem
with a different approach in
https://github.com/rust-lang/rust/pull/161450<https://urldefense.com/v3/__https://github.com/rust-lang/rust/pull/161450__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW5_rpjPaQ$>, which is still open.
Alejandro's StableCrateId patch is not included: the value it pins is
already host-independent in our builds, and it broke three rust test
suite cases when the autobuilder tested it.
Tested on the autobuilder: the x86 reproducible builder green with
zero differing packages, the rust test suite green, and on both arm
builders rust, rust-dbg, rust-rustdoc and libstd-rs-dev gone from the
failing list.
Sunil Dora (5):
rust: drop the cc object-name reproducibility patch
rust: hash cc object names relative to their source roots
rust: keep the build host triple out of cargo unit metadata
rust: backport deterministic DocLinkResMap serialisation
rust: sort hygiene data before it is encoded
...-host-triple-from-unit-metadata-hash.patch | 62 ++++++++++
...oc-link-metadata-order-deterministic.patch | 40 ++++++
...hygiene-encoding-order-deterministic.patch | 58 +++++++++
...ject-names-relative-to-source-roots.patch} | 116 +++++++++---------
meta/recipes-devtools/rust/rust-source.inc<https://urldefense.com/v3/__http://rust-source.inc__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW5pCv2TAA$> | 5 +-
5 files changed, 224 insertions(+), 57 deletions(-)
create mode 100644 meta/recipes-devtools/rust/files/0007-cargo-omit-host-triple-from-unit-metadata-hash.patch
create mode 100644 meta/recipes-devtools/rust/files/0008-rustc-hir-make-doc-link-metadata-order-deterministic.patch
create mode 100644 meta/recipes-devtools/rust/files/0009-rustc-span-make-hygiene-encoding-order-deterministic.patch
rename meta/recipes-devtools/rust/files/{repro-issue-fix-with-cc-crate-hashmap.patch => cc-hash-object-names-relative-to-source-roots.patch} (70%)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245843): https://lists.openembedded.org/g/openembedded-core/message/245843<https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/message/245843__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW4QtYWkrg$>
Mute This Topic: https://lists.openembedded.org/mt/121261374/4354175<https://urldefense.com/v3/__https://lists.openembedded.org/mt/121261374/4354175__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW4RTLA2Tw$>
Group Owner: openembedded-core+owner@lists.openembedded.org<mailto:openembedded-core+owner@lists.openembedded.org>
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub<https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/unsub__;!!AjveYdw8EvQ!bAZjXNFQVd7FZGNUYCD78uEwFODIFOwfzeAgrtyk8STWe6WGkL_Vzz465VBcVThqLu12-qJFkYBIO_U1bW6OY1T4lQ$> [alhe@linux.microsoft.com<mailto:alhe@linux.microsoft.com>]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 8850 bytes --]
next prev parent reply other threads:[~2026-09-15 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:18 [PATCH 0/5] rust: reproducibility fixes for arm build hosts sunilkumar.dora
2026-09-15 14:18 ` [PATCH 1/5] rust: drop the cc object-name reproducibility patch sunilkumar.dora
2026-09-15 14:18 ` [PATCH 2/5] rust: hash cc object names relative to their source roots sunilkumar.dora
2026-09-15 14:18 ` [PATCH 3/5] rust: keep the build host triple out of cargo unit metadata sunilkumar.dora
2026-09-15 14:18 ` [PATCH 4/5] rust: backport deterministic DocLinkResMap serialisation sunilkumar.dora
2026-09-15 14:18 ` [PATCH 5/5] rust: sort hygiene data before it is encoded sunilkumar.dora
2026-09-15 15:53 ` [OE-core] [PATCH 0/5] rust: reproducibility fixes for arm build hosts Alejandro Hernandez
2026-09-15 16:10 ` Dora, Sunil Kumar [this message]
[not found] ` <18D58A6B209991A8.1909126@lists.openembedded.org>
2026-09-15 17:55 ` Dora, Sunil Kumar
2026-09-16 7:11 ` Antonin Godard
2026-09-21 9:46 ` Richard Purdie
2026-09-21 21:43 ` Alejandro Hernandez
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=1b9e30b7-6836-4ff7-a716-b7e87bf3d51e@windriver.com \
--to=sunilkumar.dora@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=alejandro@enedino.org \
--cc=alhe@linux.microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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