public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "mark.yang" <mark.yang@lge.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] llvm: add binutils-plugin PACKAGECONFIG for LLVMgold.so
Date: Tue, 24 Mar 2026 16:57:37 -0700	[thread overview]
Message-ID: <564384.1774396657215756194@lists.openembedded.org> (raw)
In-Reply-To: <20260324232734.2081279-1-mark.yang@lge.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

This patch is an update to following patches.
https://lists.openembedded.org/g/openembedded-core/topic/117252728 [PATCH] llvm: enable LLVMgold.so build by adding binutils dependency
https://lists.openembedded.org/g/openembedded-core/topic/patch_v2_llvm_enable/117274480 [PATCH v2] llvm: enable LLVMgold.so build by adding binutils dependency

When build component using clang that utilize lto, and when the LLD linker connot be used (Use bfd), the LLVMgold.so plugin is required in the native sysroot.
LLVMgold.so plugin is generated when binutils-plugin is enabled.
libLTO.so.21.1 is generated on the target even if it is not enabled.

The reason they were bundled in to the same package is to distribute them via the nativesdk package.

As Deepesh suggested, I mae it possible to enable this via the binutils-plugin rather than having it always built into LLVM.
The name "binutils-plugin" was inspired by gentoo's name convention. https://packages.gentoo.org/useflags/binutils-plugin

[-- Attachment #2: Type: text/html, Size: 1236 bytes --]

  reply	other threads:[~2026-03-24 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 23:27 [PATCH] llvm: add binutils-plugin PACKAGECONFIG for LLVMgold.so mark.yang
2026-03-24 23:57 ` mark.yang [this message]
2026-04-29  0:16 ` mark.yang

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=564384.1774396657215756194@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