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/releas e/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.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#176823): https://lists.openembedded.org/g/openembedded-core/message/176823 Mute This Topic: https://lists.openembedded.org/mt/96811314/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
