From: richard.purdie@linuxfoundation.org
To: Sundeep KOKKONDA <sundeep.kokkonda@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V4] meta: rust - Bug fix for target definitions returning 'NoneType' for arm
Date: Tue, 24 May 2022 12:04:20 +0100 [thread overview]
Message-ID: <3206ab3223db09451e03becdf55d972789105e18.camel@linuxfoundation.org> (raw)
In-Reply-To: <10389.1653387718015832235@lists.openembedded.org>
On Tue, 2022-05-24 at 03:21 -0700, Sundeep KOKKONDA wrote:
> Hello Richard,
>
> The patch you sent in rust-common.bbclass fixing the 'oe-selftest -r
> sstatetests.SStateTests.test_sstate_allarch_samesigs' test issue but
> the regression test shows that the
> 'sstatetests.SStateTests.test_sstate_32_64_same_hash' is getting
> failed. So, I think this change is not correct. With this patch, the
> diffsigs shows 'rust-native' sigdata is changed based on the changed
> value for RUST_TARGET_SYS variable (in x86_64 :: x86_64-unknown-
> linux-gnu & in i686 :: i686-unknown-linux-gnu). I tried several
> attempts to fix it but nothing worked out yet.
You should have seen a further couple of patches which fixed other
issues and with current master, the issues should be resolved?
Cheers,
Richard
next prev parent reply other threads:[~2022-05-24 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 5:59 [PATCH V4] meta: rust - Bug fix for target definitions returning 'NoneType' for arm Sundeep KOKKONDA
2022-05-14 7:16 ` [OE-core] " richard.purdie
2022-05-19 11:11 ` Sundeep KOKKONDA
2022-05-20 9:07 ` Alexander Kanavin
2022-05-20 9:56 ` richard.purdie
[not found] ` <16F0C7AB36B6A2B7.30875@lists.openembedded.org>
2022-05-20 11:04 ` richard.purdie
[not found] ` <16F0CB5E9328617C.25584@lists.openembedded.org>
2022-05-20 22:02 ` richard.purdie
2022-05-24 10:21 ` Sundeep KOKKONDA
2022-05-24 11:04 ` richard.purdie [this message]
2022-05-24 11:22 ` [OE-core] " Sundeep KOKKONDA
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=3206ab3223db09451e03becdf55d972789105e18.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sundeep.kokkonda@gmail.com \
/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