From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: clang/llvm 23.1.0 upgrade for oe-core
Date: Fri, 28 Aug 2026 23:23:03 -0700 [thread overview]
Message-ID: <2894840.1787984583874976123@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1sqVLefx-rJ_vdBAWqNaLtAjykHKb47EL9jttKfxcmKwcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hi Khem,
I tested the meta-oe layers against the clang/llvm 23.1.0 series, both locally and on the autobuilder (meta-oe builder, build 1754).
Two recipes need fixing. I have sent patches for both to openembedded-devel:
*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 are already fixed upstream but the fixes are not in a release yet, and meta-oe is on the newest tag of both,
so the patches are backports. Both upstream fixes are guarded on LLVM_VERSION_MAJOR, so older Clang keeps working.
perfetto builds fine, and so does include-what-you-use.
xdp-tools fails at its check_abi step with TOOLCHAIN=clang, but it fails the same way with clang 22.1.8, so it is not caused by the upgrade. I have not sent anything for it.
The autobuilder run also shows krb5, redis, tailscale and doxygen failing. None of them depends on clang or llvm, and they fail with gcc as well. Most of the error output in that run is vboxguestdrivers basehash non-determinism, which does not fail any task.
Thanks,
Sunil
[-- Attachment #2: Type: text/html, Size: 1573 bytes --]
next prev parent reply other threads:[~2026-08-29 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DS0PR11MB7901641887C85593E522BD3BE0AC2@DS0PR11MB7901.namprd11.prod.outlook.com>
2026-08-28 23:36 ` clang/llvm 23.1.0 upgrade for oe-core Khem Raj
2026-08-29 2:28 ` Dora, Sunil Kumar
2026-08-29 6:23 ` Dora, Sunil Kumar [this message]
2026-08-29 14:22 ` Dora, Sunil Kumar
2026-08-28 17:14 Dora, Sunil Kumar
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=2894840.1787984583874976123@lists.openembedded.org \
--to=sunilkumar.dora@windriver.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