All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] rust: Avoid passing host-specific information to crates Strict Version Hash
Date: Wed, 26 Aug 2026 11:25:49 -0700	[thread overview]
Message-ID: <2326647.1787768749336187635@lists.openembedded.org> (raw)
In-Reply-To: <20260826155417.2774608-1-alhe@linux.microsoft.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Hi Alejandro,

Thanks for chasing this one down. Small notes on v3:

The commit is tagged [YOCTO #15554], but that bug is "reproducibility
failures with 'rustdoc' on rust 1.75" (path-length dependent), RESOLVED FIXED
since 2024-08-01 via codegen-units=1 / lto=off.

What you describe here - artifacts differing by build host arch, causing
cross-architecture sstate matches - looks like:

[YOCTO #16376] AB-INT: build system architecture reproducibility issue
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16376

which is still open. Could you retag it in v4, unless you had a reason to
point at 15554 that I'm missing?
---
One pointer that may or may not be relevant: the 1.97.1 upgrade (65271a5d3b)
carries an LLVM backport:

0043-LoopUnroll-Iterate-exit-fold-candidates-in-determini.patch

added for a repro issue seen with rust 1.97.0. I haven't looked at whether it
interacts with the SVH path at all - just flagging it in case it's useful context.

Thanks,
Sunil Dora

[-- Attachment #2: Type: text/html, Size: 1140 bytes --]

  reply	other threads:[~2026-08-26 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 15:54 [PATCH v3] rust: Avoid passing host-specific information to crates Strict Version Hash Alejandro Hernandez
2026-08-26 18:25 ` Dora, Sunil Kumar [this message]
2026-08-26 19:17   ` [OE-core] " Richard Purdie
2026-08-26 20:08     ` Alejandro Hernandez
2026-08-26 20:47       ` Richard Purdie
     [not found]       ` <18CF75EE37DB8543.642712@lists.openembedded.org>
2026-08-27  7:53         ` Richard Purdie
2026-08-28 15:46           ` Alejandro Hernandez
2026-08-28 17:56             ` Richard Purdie
2026-09-03 18:40               ` Dora, Sunil Kumar

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=2326647.1787768749336187635@lists.openembedded.org \
    --to=sunilkumar.dora@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.