All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: alex.kanavin@gmail.com, Yash Shinde <Yash.Shinde@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"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: Thu, 29 May 2025 19:32:11 -0700	[thread overview]
Message-ID: <7571c07b-2225-4449-8169-08b044208072@gmail.com> (raw)
In-Reply-To: <CANNYZj-JtVtjk2e+Z=OmVF8RaygO5M1e+6tbQuTZYotbYetQrg@mail.gmail.com>



On 5/27/25 9:26 AM, Alexander Kanavin via lists.openembedded.org wrote:
> On Tue, 27 May 2025 at 16:42, Yash Shinde <Yash.Shinde@windriver.com> wrote:
>> Yeah, that's the reason.
>>
>> I am not sure how rust-lld is installed in ${D} now. A similar error was
>> previously resolved by using:
>> "+TARGET_CC_ARCH +=
>> "${LDFLAGS}""(https://git.yoctoproject.org/poky/commit/?id=cc24a0ff76f2e227cc3a0f478d078b2158299a80)
>>
>> LDFLAGS are explicitly unset in rust recipe.
>> (https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/rust/rust_1.85.1.bb#n194)
>> I attempted to remove the "unset LDFLAGS" in rust recipe and exported
>> TARGET_CC_ARCH as above, but that didn't work.
>>
>> Is there some different or recommended way to pass LDFLAGS to rust that
>> I might be missing?
> 
> The issue isn't about how to pass LDFLAGS. The issue is that something
> triggers building all these additional things, including rust-lld, and
> you need to narrow down how and where that happens, and how to go back
> to the install set (and build times) we've had in 1.85. Please get to
> the particular point where that decision happens.
> 
> We can't just double the build times without a comprehensive,
> convincing investigation.
> 

Try adding

[rust]
lld = false

to config.toml, but lld might speed up rust packages themselves. So 
perhaps this should be capped under a packageconfig or such, provided 
this works.

> Alex
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#217316): https://lists.openembedded.org/g/openembedded-core/message/217316
> Mute This Topic: https://lists.openembedded.org/mt/113268009/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2025-05-30  2:32 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
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 [this message]
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=7571c07b-2225-4449-8169-08b044208072@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Yash.Shinde@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 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.