Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Rust reproducibility issue summary
Date: Mon, 24 Jun 2024 02:07:28 -0700	[thread overview]
Message-ID: <2056.1719220048661049006@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj-3XSUJ5S+ewGE9owxtd4CmOps-D=5kU+MrRXoJN0pDpw@mail.gmail.com>

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

On Mon, Jun 24, 2024 at 01:50 PM, Alexander Kanavin wrote:

> 
> This is not the case. I just built rust (without sstate, from sources)
> in two different build directories on the same machine, and indeed

Thanks for sharing this... Unfortunately I couldn't see this happening during my testing. If this is the case, the issue might be there in rust.

for me diff is not there...
> diff -uNr build-b/tmp/work/core2-64-poky-linux/rust/1.75.0/image/ build-c/tmp/work/core2-64-poky-linux/rust/1.75.0/image/
> diff build-b/tmp/work/core2-64-poky-linux/rust/1.75.0/image/usr/bin/rustdoc build-c/tmp/work/core2-64-poky-linux/rust/1.75.0/image/usr/bin/rustdoc
> diff -uNr build-b/tmp/deploy/deb/core2-64/ build-c/tmp/deploy/deb/core2-64/

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

  reply	other threads:[~2024-06-24  9:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 13:28 Rust reproducibility issue summary Richard Purdie
2024-05-31 13:33 ` Patchtest results for " patchtest
2024-06-01 10:27 ` [OE-core] " Alexander Kanavin
2024-06-03  4:23   ` Sundeep KOKKONDA
2024-06-03  7:08     ` Sundeep KOKKONDA
2024-06-03  9:54       ` Alexander Kanavin
2024-06-24  3:59         ` Sundeep KOKKONDA
2024-06-24  8:20           ` [OE-core] " Alexander Kanavin
2024-06-24  9:07             ` Sundeep KOKKONDA [this message]
2024-06-24  9:11               ` Alexander Kanavin
     [not found]                 ` <12dd26bc-91c1-4af7-b756-ff42967fe5f6@windriver.com>
     [not found]                   ` <CANNYZj-jWdnRXTbFL0fMYvbVTAeSBi3qka9WgcixrMPsf7Tmww@mail.gmail.com>
2024-07-03  8:09                     ` Sundeep KOKKONDA
2024-07-03  9:58                       ` Alexander Kanavin
2024-07-04 15:13                         ` Sundeep KOKKONDA
2024-07-04 15:21                           ` [OE-core] " Alexander Kanavin
2024-07-04 16:47                             ` Randy MacLeod
2024-07-05 11:36                               ` Alexander Kanavin
2024-07-07  6:24                                 ` Sundeep KOKKONDA
     [not found]               ` <17DBE5C236FF6606.28936@lists.openembedded.org>
2024-06-24 12:22                 ` [OE-core] " Alexander Kanavin
2024-06-25  3:02                   ` Sundeep KOKKONDA
2024-06-25  9:06                     ` Alexander Kanavin
2024-07-05 15:25       ` Alexander Kanavin
2024-07-07  7:12         ` Sundeep KOKKONDA

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=2056.1719220048661049006@lists.openembedded.org \
    --to=sundeep.kokkonda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox