From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yash.Shinde@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Umesh.Kallapa@windriver.com,
Naveen.Gowda@windriver.com, Sundeep.Kokkonda@windriver.com,
Shivaprasad.Moodalappa@windriver.com
Subject: Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.
Date: Tue, 23 Jan 2024 20:07:12 +0000 [thread overview]
Message-ID: <36cf600e720193cac28386b4b4cf55f168f4058a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240123131633.641012-1-Yash.Shinde@windriver.com>
On Tue, 2024-01-23 at 05:16 -0800, Shinde, Yash via
lists.openembedded.org wrote:
> From: Yash Shinde <Yash.Shinde@windriver.com>
>
> Fixes: Exception: no cargo executable found at
> `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
>
> Fix the cargo binary path error on oe-selftest and path set to rust-snapshot dir.
>
> Patch sent to upstream- https://github.com/rust-lang/rust/pull/120125
>
> Signed-off-by: Yash Shinde <Yash.Shinde@windriver.com>
> ---
> .../rust/files/cargo-path.patch | 37 +++++++++++++++++++
> 1 file changed, 37 insertions(+)
> create mode 100644 meta/recipes-devtools/rust/files/cargo-path.patch
Unlike earlier versions of this series, there were a lot of failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6482
Basically every machine except qemumips failed on the toolchain tests.
Cheers,
Richard
next prev parent reply other threads:[~2024-01-23 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 13:16 [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 2/7] rust: detect user-specified custom targets in compiletest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 3/7] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 4/7] rust: Fix assertion failure error on oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 5/7] rust: Add new tests in the exclude list for rust oe-selftest Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 6/7] rust: Remove the test cases whose parent dir is also present in the exclude list Yash.Shinde
2024-01-23 13:16 ` [PATCH v3 7/7] rust: Enable rust oe-selftest Yash.Shinde
2024-01-23 20:07 ` Richard Purdie [this message]
2024-01-24 6:48 ` [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir Yash Shinde
[not found] ` <17AD12BD124D26C8.31068@lists.openembedded.org>
2024-01-23 21:17 ` Richard Purdie
2024-01-24 6:50 ` Yash Shinde
2024-01-24 10:21 ` Richard Purdie
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=36cf600e720193cac28386b4b4cf55f168f4058a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Naveen.Gowda@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=Umesh.Kallapa@windriver.com \
--cc=Yash.Shinde@windriver.com \
--cc=openembedded-core@lists.openembedded.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