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 v2 1/5] rust: Fetch cargo from rust-snapshot dir.
Date: Sat, 20 Jan 2024 08:42:41 +0000 [thread overview]
Message-ID: <05cf240638f79ebcceca3faa4784f366cc9bba95.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240119150907.3840110-1-Yash.Shinde@windriver.com>
On Fri, 2024-01-19 at 07:09 -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
The series failed on mips in testing:
https://autobuilder.yoctoproject.org/typhoon/#/builders/147/builds/1196/steps/12/logs/stdio
Sadly the error redirection is to a file and even in the failed build,
we do not have that file as far as I can see so it is hard to know what
went wrong.
I'm not sure how much we care about mips+rust so if we did want to skip
the tests there, I'd not be against that.
Cheers,
Richard
next prev parent reply other threads:[~2024-01-20 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 15:09 [PATCH v2 1/5] rust: Fetch cargo from rust-snapshot dir Yash.Shinde
2024-01-19 15:09 ` [PATCH v2 2/5] rust: detect user-specified custom targets in compiletest Yash.Shinde
2024-01-19 15:09 ` [PATCH v2 3/5] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest Yash.Shinde
2024-01-19 15:09 ` [PATCH v2 4/5] rust: Fix assertion failure error on oe-selftest Yash.Shinde
2024-01-19 15:09 ` [PATCH v2 5/5] rust: Enable rust oe-selftest Yash.Shinde
2024-01-20 17:01 ` Randy MacLeod
2024-01-22 10:59 ` Yash Shinde
2024-01-22 11:01 ` Shinde, Yash
2024-01-20 8:42 ` Richard Purdie [this message]
[not found] ` <17AC01A476481111.16230@lists.openembedded.org>
2024-01-20 8:49 ` [OE-core] [PATCH v2 1/5] rust: Fetch cargo from rust-snapshot dir Richard Purdie
2024-01-20 10:46 ` Yash Shinde
2024-01-20 17:03 ` Randy MacLeod
2024-01-22 10:58 ` 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=05cf240638f79ebcceca3faa4784f366cc9bba95.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