From: "mark.yang" <mark.yang@lge.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] llvm: enable LLVMgold.so build by adding binutils dependency
Date: Mon, 19 Jan 2026 14:23:57 -0800 [thread overview]
Message-ID: <211003.1768861437348499871@lists.openembedded.org> (raw)
In-Reply-To: <437B0EEA-925C-40BD-BA9B-7773BBEEE9F1@arm.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Ross Burton, thank you for the review.
The build reproduction steps and the intention for this patch can be found in the v1 patch at https://lists.openembedded.org/g/openembedded-core/topic/117252728.
PACKAGECONFIG:remove:class-native = "lto thin-lto"
Due to the configuration, llvm-native cannot enable lto in PACKAGECONFIG in any way.
When attempting to use clang + lto, components that cannot use the lld linker (and instead use the bfd linker) require the LLVMgold.so plugin.
To achieve this, binutils and the -DLLVM_BINUTILS_INCDIR flag in CMake are required.
( https://github.com/llvm/llvm-project/blob/main/clang/docs/ThinLTO.rst#basic )
Anyway, llvm-native cannot have LTO enabled due to the `remove`.
-DLLVM_ENABLE_LTO=Full determines whether LLVM itself will be built with LTO applied.
However, even if LLVM is not built using LTO, I think the environment should still be configured so that other components using the LLVM/clang toolchain can use LTO.
[-- Attachment #2: Type: text/html, Size: 1404 bytes --]
next prev parent reply other threads:[~2026-01-19 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 4:24 [PATCH v2] llvm: enable LLVMgold.so build by adding binutils dependency mark.yang
2026-01-19 18:12 ` [OE-core] " Ross Burton
2026-01-19 22:23 ` mark.yang [this message]
2026-03-03 10:37 ` Varatharajan, Deepesh
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=211003.1768861437348499871@lists.openembedded.org \
--to=mark.yang@lge.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox