From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Yocto reproducibilty issue :: rust-llvm binary differences
Date: Tue, 21 Feb 2023 22:11:57 -0800 [thread overview]
Message-ID: <17248.1677046317939376137@lists.openembedded.org> (raw)
In-Reply-To: <24955.1677038318936477992@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Additional object files link (if needed) -> https://we.tl/t-RvgWukdcFB
poky/build-llvm-A/tmp/work/x86_64-linux/rust-native/ -> rust-native-A-obj.tar
poky/build-llvm-B/tmp/work/x86_64-linux/rust-native/ -> rust-native-B-obj.tar
poky/build-llvm-A/tmp/work/x86_64-linux/rust-llvm-native/ -> rust-llvm-native-A-obj.tar
poky/build-llvm-B/tmp/work/x86_64-linux/rust-llvm-native/ -> rust-llvm-native-B-obj.tar
>
> $ diff -ur rust-llvm-native-A-obj rust-llvm-native-B-obj
> Binary files rust-llvm-native-A-obj/llvm-config.cpp.o and
> rust-llvm-native-B-obj/llvm-config.cpp.o differ
> Binary files rust-llvm-native-A-obj/python.o and
> rust-llvm-native-B-obj/python.o differ
>
> $ diff -ur rust-native-A-obj rust-native-B-obj
> Binary files rust-native-A-obj/1mg8n9voykv9ib2d.o and
> rust-native-B-obj/1mg8n9voykv9ib2d.o differ
> Binary files rust-native-A-obj/538dmycheh7dlbck.o and
> rust-native-B-obj/538dmycheh7dlbck.o differ
> Binary files rust-native-A-obj/python.o and rust-native-B-obj/python.o
> differ
>
[-- Attachment #2: Type: text/html, Size: 1352 bytes --]
next prev parent reply other threads:[~2023-02-22 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 16:47 Yocto reproducibilty issue :: rust-llvm binary differences Kokkonda, Sundeep
2023-02-21 17:51 ` [OE-core] " Alexander Kanavin
2023-02-22 3:58 ` Sundeep KOKKONDA
2023-02-22 6:11 ` Sundeep KOKKONDA [this message]
2023-02-22 11:09 ` [OE-core] " Alexander Kanavin
2023-02-22 19:45 ` Khem Raj
2023-03-01 6:28 ` Sundeep KOKKONDA
2023-03-01 6:47 ` [OE-core] " Alexander Kanavin
2023-03-01 8:21 ` Richard Purdie
2023-03-01 8:26 ` Richard Purdie
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=17248.1677046317939376137@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