Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: sunilkumar.dora@windriver.com
To: openembedded-devel@lists.openembedded.org
Cc: raj.khem@gmail.com, deepesh.varatharajan@windriver.com,
	sundeep.kokkonda@windriver.com
Subject: [meta-oe][PATCH 0/2] Fix bcc and castxml builds with LLVM 23
Date: Sat, 29 Aug 2026 11:35:18 +0530	[thread overview]
Message-ID: <20260829060520.2905173-1-sunilkumar.dora@windriver.com> (raw)

From: Sunil Dora <sunilkumar.dora@windriver.com>

oe-core is moving clang/llvm from 22.1.8 to 23.1.0. Two recipes in
meta-oe do not build against 23, because upstream LLVM and Clang changed
APIs they use:

  castxml  Clang 23 renamed ASTContext::getRawCommentForDeclNoCache to
           getRawCommentNoCache.
  bcc      LLVM 23 changed the MCContext constructor to take MCAsmInfo,
           MCRegisterInfo and MCSubtargetInfo by reference rather than
           by pointer.

Both projects have already fixed this upstream, but neither fix is in a
release yet, and meta-oe is already on the newest tag of both. So these
are backports rather than version bumps.

Both upstream fixes are guarded on LLVM_VERSION_MAJOR, so the recipes
keep building with older Clang.

Both failures also reproduce on the Yocto autobuilder meta-oe world
build run against the oe-core clang/llvm 23.1.0 series.

Tested on qemux86-64 with meta-oe and meta-python on top of the oe-core
clang/llvm 23.1.0 series: castxml and bcc both build, with the default
gcc toolchain and with TOOLCHAIN=clang.

Sunil Dora (2):
  castxml: Fix build with LLVM 23
  bcc: Fix build with LLVM 23

 ...ix-MCContext-constructor-for-LLVM-23.patch | 36 +++++++++++++++++++
 .../recipes-devtools/bcc/bcc_0.37.0.bb        |  1 +
 .../castxml/0001-Port-to-LLVM-Clang-23.patch  | 36 +++++++++++++++++++
 .../recipes-devtools/castxml/castxml_0.7.0.bb |  4 ++-
 4 files changed, 76 insertions(+), 1 deletion(-)
 create mode 100644 meta-oe/dynamic-layers/meta-python/recipes-devtools/bcc/bcc/0001-src-cc-Fix-MCContext-constructor-for-LLVM-23.patch
 create mode 100644 meta-oe/recipes-devtools/castxml/castxml/0001-Port-to-LLVM-Clang-23.patch

-- 
2.43.0



             reply	other threads:[~2026-08-29  6:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29  6:05 sunilkumar.dora [this message]
2026-08-29  6:05 ` [meta-oe][PATCH 1/2] castxml: Fix build with LLVM 23 sunilkumar.dora
2026-08-29  6:05 ` [meta-oe][PATCH 2/2] bcc: " sunilkumar.dora

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=20260829060520.2905173-1-sunilkumar.dora@windriver.com \
    --to=sunilkumar.dora@windriver.com \
    --cc=deepesh.varatharajan@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=sundeep.kokkonda@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