From: Ross Burton <Ross.Burton@arm.com>
To: "raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] toolchain/classes: Add lld-native dependency when using lld as system linker
Date: Mon, 12 Jan 2026 16:17:16 +0000 [thread overview]
Message-ID: <03D1C411-B650-46E3-9644-7FDB94DF8CBC@arm.com> (raw)
In-Reply-To: <20251230064832.2257911-1-raj.khem@gmail.com>
> On 30 Dec 2025, at 06:48, Khem Raj via lists.openembedded.org <raj.khem=gmail.com@lists.openembedded.org> wrote:
>
> This was not an issue before lld split from clang, but now its an independent
> recipe and needs to be brought into dependency chain, otherwise clang fails to
> build with -flto as it does not find gold or lld plugins.
Conditional python in a very core variable like this isn’t ideal, and the clang-cross recipe already has this dependency. Is that not sufficient, or is there some edge case where that dependency isn’t enough?
Ross
next prev parent reply other threads:[~2026-01-12 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 6:48 [PATCH] toolchain/classes: Add lld-native dependency when using lld as system linker Khem Raj
2026-01-12 16:17 ` Ross Burton [this message]
2026-01-12 16:25 ` [OE-core] " Khem Raj
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=03D1C411-B650-46E3-9644-7FDB94DF8CBC@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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