From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1634C636D4 for ; Tue, 7 Feb 2023 16:58:22 +0000 (UTC) Received: from mail-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) by mx.groups.io with SMTP id smtpd.web11.88863.1675789093891853020 for ; Tue, 07 Feb 2023 08:58:13 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=D3e7s8Ew; spf=pass (domain: gmail.com, ip: 209.85.216.48, mailfrom: sundeep.kokkonda@gmail.com) Received: by mail-pj1-f48.google.com with SMTP id bx22so12728356pjb.3 for ; Tue, 07 Feb 2023 08:58:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=4XbkiiXf6/UKcQlbxFG5aKQHQENQWRBPYTGGeQG6S5Q=; b=D3e7s8EwxlLq3yCUNpSqEYTBn/PX3Gn6CgHvUm9nNdQ8f//ppEuw0o74Ovg8HtyaKA f8LslJxrYxo1/bAxG9er1QTwE6J/RrDO5HR5dN0DwzgXtuFDsv8IrVYBJg5HAOOjO4mI uTuRkprtnqky53WgStOTPk9nrTlZ08eWPD3A4DLcMUWk9vwNPFSjYLb36qvusNWmlr1R CAABeoICvNlVr2CJ8CE1myVnR+I2GkJm2LDp7/elaSSDlTM5+cHpBdBO7AAjVA+6Qz+O CcA5yTOqZ6BuavUcA0ucJuiD3D49y8zTpY6KWWMQpO4uaVs3VPQo8he+ShzQsxT1qGMm 6p/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :cc:to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4XbkiiXf6/UKcQlbxFG5aKQHQENQWRBPYTGGeQG6S5Q=; b=hw00ZxMEUVXubknaCFl3NRUPr6EQHwIuWvCGR+MG37mMnIvbkxn1vSfXPKFD8aJYPR Tjy0jfbLFChDzI0G79iaZFSITo48n0MI5AXV3jdIn6tvFlde7ZayTyfBl5iyk66JS/52 un7/06MOkc4PRxkFzGoune+tPLQNt6xVdla8B+Qh2oMiQdEYFXyeIr6l7Zkc5vWmpQ7/ Huyarj5NdmhrYl/OwqQXJ/sSERWUHzoFrT9YSfD+aoWj2ttVWHXFmIcTrrCTCrRJOB67 bh5fpTT3RJQzUuDK5ZIRKaJ6Xb0wBa3AIzpR2TW3OyqnLo+1pyXUxcDvn6Vhlg3byzCF tYrw== X-Gm-Message-State: AO0yUKVx7f1Jx2NSBwZJ9VszBTI4O0c7OOSCGpWv6RDUtPV6OVOymIP1 PZXBDKr7sPtATzM+NJAlwj2d9Kmt5ss/9w== X-Google-Smtp-Source: AK7set8rIA7uv/luqQpJV6PlqKGK+BeJlwOllOgBA/PxfCNvkJYW2zBoOkdvR8g6VbfpABy+Hxsn1A== X-Received: by 2002:a05:6a20:8401:b0:c0:afba:8b78 with SMTP id c1-20020a056a20840100b000c0afba8b78mr5071192pzd.45.1675789093009; Tue, 07 Feb 2023 08:58:13 -0800 (PST) Received: from BFTLPTI009 ([183.83.146.245]) by smtp.gmail.com with ESMTPSA id jj4-20020a170903048400b001990028c0c9sm1560336plb.68.2023.02.07.08.58.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2023 08:58:12 -0800 (PST) From: To: "'\"Alex Kiernan\"'" , "'Richard Purdie'" Cc: , "'Randy MacLeod'" Subject: Yocto Bug 14965 - Need info on rmeta hash Date: Tue, 7 Feb 2023 22:28:08 +0530 Message-ID: <003001d93b15$5c8396e0$158ac4a0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01D93B43.763CE450" X-Mailer: Microsoft Outlook 16.0 Thread-Index: Adk7FLu8Trw3aqMsT5OBSa3qgvxE5A== Content-Language: en-in List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 07 Feb 2023 16:58:22 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/176823 This is a multipart message in MIME format. ------=_NextPart_000_0031_01D93B43.763CE450 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. ------=_NextPart_000_0031_01D93B43.763CE450 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello = Alex,

&n= bsp;

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.

&n= bsp;

I = found that the changes with below commit id causing the 2nd rmeta file = (libcore-c5fc82c620226960.rmeta) = generation.

e33afcd= 0dc rust-common.bbclass: use built-in rust targets for -native = builds

&n= bsp;

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.<= /li>
  • The dependency files = (../build/tmp/work/core2-64-poky-linux/librsvg/2.54.5-r0/build/target/rel= ease/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).<= /li>
  • But, some interesting = changes I observed in '.rustc_info.json' which are related = to e33afcd0dc commit. In this json file,<= /li>
    • 'host' tag changed from = 'x86_64-linux-gnu' -> 'x86_64-unknown-linux-gnu',<= /li>
    • an extra = 'target_feature=3D\"fxsr\' is added, and<= /li>
    • ‘rustc_fingerprint= ’ has different values between 2 builds.

      <= /li>

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?

&n= bsp;

&n= bsp;

Thanks,=

Sundeep= K.

 

------=_NextPart_000_0031_01D93B43.763CE450--