Hi Sundeep Not sure I can really help - at best I'm a novice rust user (albeit with a team who are writing rust).
Looking at the source for rmeta generation (https://github.com/rust-lang/rust/tree/master/compiler/rustc_metadata/src/rmeta) it looks like it's really just a dump of internal state. So I'd expect pretty much anything can cause it to change - running strings over a couple of files I have here I see things like the compiler triple in there and the paths to source files. Given we're seeing this in libstd-rs, I wonder if this is really an issue with how we're building libstd-rs - as far as I can tell the (current) supported way to build it is as part of the whole compiler build. Looking at the arch build by comparison its all in one pass, albeit with no need for separate native/target complications: https://github.com/archlinux/svntogit-packages/blob/packages/rust/trunk/PKGBUILD Though I don't know how you'd fit that into our world. On Tue, Feb 7, 2023 at 4:58 PM <sundeep.kokko...@gmail.com> wrote: > > Hello Alex, > > > > I am working on Yocto bug 14965. There is a build failure happening during > rust build because of 2 rmeta files with different hashes are generated. > > > > I found that the changes with below commit id causing the 2nd rmeta file > (libcore-c5fc82c620226960.rmeta) generation. > > e33afcd0dc rust-common.bbclass: use built-in rust targets for -native builds > > > > I am trying to find the changes in build which causing the generation of 2nd > rmeta with different hash. I gave 2 builds by with & without e33afcd0dc > commit changes. > > I checked the sigdata of librsvg & libstd-rs in both builds and those are > identical. > The dependency files > (../build/tmp/work/core2-64-poky-linux/librsvg/2.54.5-r0/build/target/release/deps/*.d) > also analysed and the shown differences are only the changed hash value (did > not get any info on what is causing this change). > But, some interesting changes I observed in '.rustc_info.json' which are > related to e33afcd0dc commit. In this json file, > > 'host' tag changed from 'x86_64-linux-gnu' -> 'x86_64-unknown-linux-gnu', > an extra 'target_feature=\"fxsr\' is added, and > ‘rustc_fingerprint’ has different values between 2 builds. > > Since you know much about rust, can you let me know is there any way I can > check which exact changes are causing the hash to be changed? also, are the > above changes in json file will cause hash to be changed? > > > > > > Thanks, > > Sundeep K. > > -- Alex Kiernan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#176915): https://lists.openembedded.org/g/openembedded-core/message/176915 Mute This Topic: https://lists.openembedded.org/mt/96811314/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
