public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Yash Shinde <Yash.Shinde@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
	openembedded-core@lists.openembedded.org
Cc: Umesh.Kallapa@windriver.com, Naveen.Gowda@windriver.com,
	Sundeep.Kokkonda@windriver.com,
	Shivaprasad.Moodalappa@windriver.com
Subject: Re: [PATCH v2 1/5] rust: Fetch cargo from rust-snapshot dir.
Date: Mon, 22 Jan 2024 16:28:45 +0530	[thread overview]
Message-ID: <b31714ef-7a03-4c2a-ba65-6ca633ec623a@windriver.com> (raw)
In-Reply-To: <34274d69-cab5-4e74-a167-4a72a50d9e55@windriver.com>


On 20-01-2024 22:33, Randy MacLeod wrote:
> On 2024-01-19 10:09 a.m., Yash.Shinde@windriver.com 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
>
>
> Good!
>
> It's a bit worrying that the PR pipeline failed a number of tests.
> Do you want to revise that and push a new commit there and do a v3 here?
>
I will look into the failure in the PR but for now we need this patch 
for rust oe-selftest in Yocto.

Regards,
Yash
>
> ../Randy
>
>> 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
>>
>> diff --git a/meta/recipes-devtools/rust/files/cargo-path.patch b/meta/recipes-devtools/rust/files/cargo-path.patch
>> new file mode 100644
>> index 0000000000..547df353d2
>> --- /dev/null
>> +++ b/meta/recipes-devtools/rust/files/cargo-path.patch
>> @@ -0,0 +1,37 @@
>> +Fix the cargo binary path error and ensure that it is fetched
>> +during rustc bootstrap in rust oe-selftest.
>> +
>> +======================================================================
>> +ERROR: test_cargoflags (bootstrap_test.BuildBootstrap)
>> +----------------------------------------------------------------------
>> +Traceback (most recent call last):
>> +  File "/home/build-st/tmp/work/cortexa57-poky-linux/rust/1.74.1/rustc-1.74.1-src/src/bootstrap/bootstrap_test.py", line 157, in test_cargoflags
>> +    args, _ = self.build_args(env={"CARGOFLAGS": "--timings"})
>> +  File "/home/build-st/tmp/work/cortexa57-poky-linux/rust/1.74.1/rustc-1.74.1-src/src/bootstrap/bootstrap_test.py", line 154, in build_args
>> +    return build.build_bootstrap_cmd(env), env
>> +  File "/home/build-st/tmp/work/cortexa57-poky-linux/rust/1.74.1/rustc-1.74.1-src/src/bootstrap/bootstrap.py", line 960, in build_bootstrap_cmd
>> +    raise Exception("no cargo executable found at `{}`".format(
>> +Exception: no cargo executable found at `/home/build-st/tmp/work/cortexa57-poky-linux/rust/1.74.1/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo`
>> +
>> +Upstream-Status: Submitted [https://github.com/rust-lang/rust/pull/120125]
>> +
>> +Signed-off-by: Yash Shinde<Yash.Shinde@windriver.com>
>> +---
>> +diff --git a/src/bootstrap/bootstrap.py b/src/bootstrap/bootstrap.py
>> +--- a/src/bootstrap/bootstrap.py
>> ++++ b/src/bootstrap/bootstrap.py
>> +@@ -954,9 +954,11 @@
>> +         if deny_warnings:
>> +             env["RUSTFLAGS"] += " -Dwarnings"
>> +
>> +-        env["PATH"] = os.path.join(self.bin_root(), "bin") + \
>> +-            os.pathsep + env["PATH"]
>> +-        if not os.path.isfile(self.cargo()):
>> ++        cargo_bin_path = os.path.join(self.bin_root(), "bin", "cargo")
>> ++        if not os.path.isfile(cargo_bin_path):
>> ++            cargo_bin_path = os.getenv("RUST_TARGET_PATH") + "rust-snapshot/bin/cargo"
>> ++            env["PATH"] = os.path.dirname(cargo_bin_path) + os.pathsep + env["PATH"]
>> ++        else:
>> +             raise Exception("no cargo executable found at `{}`".format(
>> +                 self.cargo()))
>> +         args = [self.cargo(), "build", "--manifest-path",
>
>
> -- 
> # Randy MacLeod
> # Wind River Linux


      reply	other threads:[~2024-01-22 10:59 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 ` [OE-core] [PATCH v2 1/5] rust: Fetch cargo from rust-snapshot dir Richard Purdie
     [not found] ` <17AC01A476481111.16230@lists.openembedded.org>
2024-01-20  8:49   ` Richard Purdie
2024-01-20 10:46     ` Yash Shinde
2024-01-20 17:03 ` Randy MacLeod
2024-01-22 10:58   ` Yash Shinde [this message]

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=b31714ef-7a03-4c2a-ba65-6ca633ec623a@windriver.com \
    --to=yash.shinde@windriver.com \
    --cc=Naveen.Gowda@windriver.com \
    --cc=Shivaprasad.Moodalappa@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Umesh.Kallapa@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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