From: Randy MacLeod <randy.macleod@windriver.com>
To: Alex Kiernan <alex.kiernan@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Yash.Shinde@windriver.com,
openembedded-core@lists.openembedded.org,
Umesh.Kallapa@windriver.com, Naveen.Gowda@windriver.com,
Sundeep.Kokkonda@windriver.com,
Shivaprasad.Moodalappa@windriver.com
Subject: Re: [OE-core] [PATCH 1/2] rust: Upgrade 1.70.0 -> 1.73.0
Date: Fri, 8 Dec 2023 09:13:52 -0500 [thread overview]
Message-ID: <0b20b0f2-9cf7-4afa-9508-91eef56d8122@windriver.com> (raw)
In-Reply-To: <CAO5Uq5RLXtwaVULLQWh_atppYvO_r-qibP7AMyE7KiLyj4SAvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
On 2023-12-08 9:07 a.m., Alex Kiernan wrote:
> On Fri, Dec 8, 2023 at 1:55 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Fri, 2023-12-08 at 13:47 +0000, Alex Kiernan wrote:
>>> On Fri, Dec 8, 2023 at 9:56 AM Shinde, Yash via lists.openembedded.org
>>> <Yash.Shinde=windriver.com@lists.openembedded.org> wrote:
>>>> From: Yash Shinde<Yash.Shinde@windriver.com>
>>>>
>>>> In rust 1.72.0 the 'mips*-unknown-linux-gnu*' support demoted from tier2 to tier3.
>>>> The mips bootstrap compiler is removed from src/stage0.json file and
>>>> so the same are removed from rust-snapshot.inc. [https://github.com/rust-lang/rust/releases/tag/1.72.0]
>>>>
>>>> Drop bootstrap_fail.patch, getrandom-open64.patch
>>>> as they are merged in upstream rust.
>>> ]>
>>>> Signed-off-by: Yash Shinde<Yash.Shinde@windriver.com>
>>>> ---
>>> If we're going to go down the road of disabling the rust oe-selftest
>>> (and I don't see a better option right now as we're well behind), I
>>> have a series which steps us through each of the releases up to
>>> 1.74.0.
>>>
>>> It also avoids the need for the library/test hack (upstream has a new
>>> target we can use for libstd).
>> This sounds useful, particularly this last piece. Can you send it? We
>> could probably combine it with 2/2 in this series if Yash/Randy agree.
>>
> I've pulled that in as the first patch in the series so if you were
> bisecting you wouldn't see the oe-selftest fail on upgrade to 1.71.
I was just about to ask you to do that! Thanks for being one step ahead
of me!
> It's on top of the cargo cleanups I posted yesterday, so I suspect
> those are prerequisites (or I could combine the two into one series?)
I'm not sure, let's see it on the list and review there.
>
> I've not tested every step extensively, but they all build and I've
> tested cargo in most of them manually inside qemu.
>
Thanks Alex.
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 3781 bytes --]
next prev parent reply other threads:[~2023-12-08 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 9:54 [PATCH 1/2] rust: Upgrade 1.70.0 -> 1.73.0 Yash.Shinde
2023-12-08 9:54 ` [PATCH 2/2] rust: Disable rust oe-selftest Yash.Shinde
2023-12-08 13:47 ` [OE-core] [PATCH 1/2] rust: Upgrade 1.70.0 -> 1.73.0 Alex Kiernan
2023-12-08 13:55 ` Richard Purdie
2023-12-08 14:07 ` Alex Kiernan
2023-12-08 14:13 ` Randy MacLeod [this message]
2023-12-08 14:50 ` Yash Shinde
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=0b20b0f2-9cf7-4afa-9508-91eef56d8122@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Naveen.Gowda@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Umesh.Kallapa@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=alex.kiernan@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox