All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Yocto Bug 14965 - Need info on rmeta hash
Date: Sun, 12 Feb 2023 23:01:32 -0800	[thread overview]
Message-ID: <21754.1676271692934287086@lists.openembedded.org> (raw)
In-Reply-To: <CAO5Uq5T4NQ=BrHBWCBC+7sSPKnfdUoUC+qLpnFtVRPdnmhtxhQ@mail.gmail.com>

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

Hello Richard,

As we discussed, I checked the build by removing the variables (RUST_BUILD_SYS, RUST_HOST_SYS & RUST_TARGET_SYS) from BB_BASEHASH_IGNORE_VARS in meta/conf/bitbake.conf file but this doesn't solve the issue, still 2 rmeta files generated.

So, I did a re-check of my analysis w.r.t to commit id - ' e33afcd0dc rust-common.bbclass: use built-in rust targets for -native builds '. The 2 nd rmeta file is generating by this commit id only and as mentioned earlier there is no diff in the generated sigdata files of libstd-rs & librsvg with this change.

May be removing vars form BB_BASEHASH_IGNORE_VARS is not a right fix?

FYI... See below generated rmeta files with and without e33afcd0dc.

> 
> :/3565ea860a-> git reflog
> 3565ea860a (HEAD) HEAD@{0}: checkout: moving from master to 3565ea860a
> aa6cd06a9f (origin/master, origin/HEAD, master) HEAD@{1}: clone: from
> git://git.yoctoproject.org/poky
> :/3565ea860a-> ls
> build/tmp/work/core2-64-poky-linux/librsvg/2.54.5-r0/recipe-sysroot/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/
> | grep libcore
> libcore- 5c7322bf8f654199.rlib
> libcore- 5c7322bf8f654199.rmeta
> 

> 
> :/e33afcd0dc-> git reflog
> e33afcd0dc (HEAD) HEAD@{0}: checkout: moving from master to e33afcd0dc
> aa6cd06a9f (origin/master, origin/HEAD, master) HEAD@{1}: clone: from
> git://git.yoctoproject.org/poky
> :/e33afcd0dc-> ls
> build/tmp/work/core2-64-poky-linux/librsvg/2.54.5-r0/recipe-sysroot/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/
> | grep libcore
> libcore- c5fc82c620226960.rlib
> libcore- c5fc82c620226960.rmeta
> 

Sigdata diff:

> 
> :/e33afcd0dc-> diff -ur build/tmp/stamps/core2-64-poky-linux/libstd-rs/
> ../3565ea860a/build/tmp/stamps/core2-64-poky-linux/libstd-rs/
> Binary files
> build/tmp/stamps/core2-64-poky-linux/libstd-rs/1.64.0-r0.do_compile.sigdata.58c969bdc47351ac51bd19dd76f57855e14940a04ff9bdfbfc5cb92a27172da8
> and
> ../3565ea860a/build/tmp/stamps/core2-64-poky-linux/libstd-rs/1.64.0-r0.do_compile.sigdata.58c969bdc47351ac51bd19dd76f57855e14940a04ff9bdfbfc5cb92a27172da8
> differ
> ....
> ....
> Binary files
> build/tmp/stamps/core2-64-poky-linux/libstd-rs/1.64.0-r0.do_unpack.sigdata.1203b8d6806ffeb75970f492ece3eaa91c51a79eb411eb075946c482239a69d5
> and
> ../3565ea860a/build/tmp/stamps/core2-64-poky-linux/libstd-rs/1.64.0-r0.do_unpack.sigdata.1203b8d6806ffeb75970f492ece3eaa91c51a79eb411eb075946c482239a69d5
> differ
> 

I checked the dumpsig of the above shown differences and the changes are only in the name of build directory.

Thanks,
Sundeep K.

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

      reply	other threads:[~2023-02-13  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 16:58 Yocto Bug 14965 - Need info on rmeta hash sundeep.kokkonda
2023-02-09  6:19 ` Alex Kiernan
2023-02-13  7:01   ` Sundeep KOKKONDA [this message]

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=21754.1676271692934287086@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 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.