From: Yash Shinde <Yash.Shinde@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Randy MacLeod <randy.macleod@windriver.com>,
openembedded-core@lists.openembedded.org,
Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Cc: Sundeep.Kokkonda@windriver.com
Subject: Re: [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0
Date: Mon, 31 Mar 2025 11:23:09 +0530 [thread overview]
Message-ID: <ae548b74-5ad0-476c-95a8-dcd5290cbf2a@windriver.com> (raw)
In-Reply-To: <12776bb304a6c5a98f34325fca117ae7a541ef2e.camel@linuxfoundation.org>
On 29-03-2025 20:56, Richard Purdie wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Fri, 2025-03-28 at 16:56 -0400, Randy MacLeod wrote:
>> On 2025-03-28 10:30 a.m., Yash.Shinde@windriver.com wrote:
>>> RUSTSRC = "${WORKDIR}/rustc-${RUST_VERSION}-src"
>>>
>>>
>>>
>>>
>>> -#After updating to Rust 1.85 we can revert this removal of "src/gcc"
>>> -remove_gcc_directory() {
>>> - # Ensure the gcc directory exists
>>> - gcc_dir="${S}/src/gcc"
>>> - if [ -d "$gcc_dir" ]; then
>>> - rm -rf "$gcc_dir"
>>> - fi
>>> -}
>>> -# Add postfunc to the do_unpack task
>>> -do_unpack[postfuncs] += "remove_gcc_directory"
>>> -
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> On IRC, Richard said:
>> I'm puzzled as the rust space fix didn't have the impact on the metrics I'd hoped for :/
>> I think there is something else going on. ...
>>
>>
>>
>>
>>
> I a look and realised the issue, the trouble is S is not always
> RUSTSRC. I've sent a patch, hopefully the metrics look better this
> time.
Thank you for looking into it and identifying the issue.
This should certainly work.
Looking forward for the results.
Regards,
Yash
> Cheers,
>
> Richard
next prev parent reply other threads:[~2025-03-31 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 14:30 [PATCH 1/3] rust: Update "do_update_snapshot" task for rust-snapshot.inc Yash.Shinde
2025-03-28 14:30 ` [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0 Yash.Shinde
2025-03-28 14:40 ` [OE-core] " Richard Purdie
2025-03-28 18:39 ` Alexander Kanavin
2025-03-31 5:51 ` Yash Shinde
2025-03-28 14:50 ` Patchtest results for " patchtest
2025-03-28 15:17 ` [OE-core] " Koen Kooi
2025-03-28 17:51 ` Richard Purdie
2025-03-31 5:52 ` Yash Shinde
2025-03-28 18:02 ` Khem Raj
2025-03-31 5:52 ` Yash Shinde
2025-03-28 20:56 ` Randy MacLeod
2025-03-29 15:26 ` Richard Purdie
2025-03-31 5:53 ` Yash Shinde [this message]
2025-03-28 14:30 ` [PATCH 3/3] rust: Upgrade 1.85.0->1.85.1 Yash.Shinde
2025-03-28 14:50 ` Patchtest results for " patchtest
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=ae548b74-5ad0-476c-95a8-dcd5290cbf2a@windriver.com \
--to=yash.shinde@windriver.com \
--cc=Deepesh.Varatharajan@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.