Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yash Shinde <Yash.Shinde@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: "MacLeod, Randy" <randy.macleod@windriver.com>,
	"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [RFC] rust: Upgrade 1.85.1->1.86.0
Date: Tue, 27 May 2025 20:10:19 +0530	[thread overview]
Message-ID: <d550759e-95e2-4be8-bde6-7af2329bc12f@windriver.com> (raw)
In-Reply-To: <CANNYZj-tN0ONWxYPb9JJms3hj0fUp_9i3xhwd=GtXsEdkXb7AA@mail.gmail.com>


On 27-05-2025 19:10, Alexander Kanavin 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 Tue, 27 May 2025 at 14:47, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
>
>> I'll try to see if ldflags issue can be addressed properly, but first
>> I have to note that there's a significant build performance regression
>> in rust-native: where 1.85 do_install finishes on my machine in under
>> 9 minutes, 1.86 from your branch took 23 minutes. You need to
>> carefully review the logs to see if somehow rust-native builds the
>> whole set of tools, rather than just the compiler. Or if it's doing a
>> full bootstrap, where 1.85 is able to avoid stage2 because it's
>> building a native compiler.
> Target rust as well regressed: 18 min -> 33 minutes. This does need to
> be addressed :-/
>
Hi Alex,

Thanks for reviewing the changes.

The Rust build now includes additional dependencies such as pkg-config, 
ninja, openssl
which are required for building rust and ensuring better compatibility 
across various build
environments.
(https://github.com/rust-lang/rust/blob/master/INSTALL.md#dependencies)

I believe the increased time is a result of theses added components as 
they can trigger
more comprehensive configuration and build steps, which naturally extend 
the overall
build time.



Regards,
Yash


  reply	other threads:[~2025-05-27 14:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 16:22 [RFC] rust: Upgrade 1.85.1->1.86.0 Yash Shinde
2025-05-27 12:47 ` [OE-core] " Alexander Kanavin
     [not found] ` <184363192F51E64D.13855@lists.openembedded.org>
2025-05-27 13:40   ` Alexander Kanavin
2025-05-27 14:40     ` Yash Shinde [this message]
2025-05-27 14:06 ` Alexander Kanavin
2025-05-27 14:42   ` Yash Shinde
2025-05-27 16:26     ` Alexander Kanavin
2025-05-30  2:32       ` Khem Raj
2025-05-30 12:42         ` Yash Shinde
2025-05-30 13:15           ` Alexander Kanavin
2025-06-02 11:15             ` Yash Shinde
2025-06-02 13:03               ` Randy MacLeod
2025-06-02 17:09                 ` Khem Raj
2025-06-03 18:31                   ` Randy MacLeod
2025-06-03 20:56                     ` Khem Raj
2025-06-06 12:50                     ` Yash Shinde
2025-06-06 12:57                       ` Yash Shinde
2025-06-03 19:14               ` Randy MacLeod

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=d550759e-95e2-4be8-bde6-7af2329bc12f@windriver.com \
    --to=yash.shinde@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=alex.kanavin@gmail.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