From: "mark.yang" <mark.yang@lge.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] kernel: make the kernel toolchain switchable to clang
Date: Tue, 07 Jul 2026 19:44:33 -0700 [thread overview]
Message-ID: <400669.1783478673234550269@lists.openembedded.org> (raw)
In-Reply-To: <CADkTA4O5hcXQxCp-pqTM0yCVLCi3Bt6T=xzZeFkMLX7f17ayyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Hi Bruce,
Bad timing on my part - I posted this before spotting Harish's series,
sorry for the noise.
It's not quite the same though: the point of this series is patches 1
and 3, keeping the kernel, out-of-tree modules and make-mod-scripts on
one toolchain. With only the kernel recipe switched to clang, modules
and make-mod-scripts still run make against the shared kernel build
tree with the gcc defaults; kbuild notices the CC_VERSION_TEXT mismatch
and re-runs syncconfig, silently dropping compiler-dependent options
from the shared .config - CONFIG_CFI_CLANG for example disappears as
soon as any out-of-tree module is built, with no error anywhere.
Reproduced on qemux86-64 with cryptodev-module.
I'll drop the two patches that overlap with Harish's series and send a
v2 with the module/make-mod-scripts side rebased on top of his.
Mark
[-- Attachment #2: Type: text/html, Size: 950 bytes --]
prev parent reply other threads:[~2026-07-08 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 2:28 [OE-core][PATCH 0/3] kernel: make the kernel toolchain switchable to clang mark.yang
2026-07-08 2:28 ` [OE-core][PATCH 1/3] module.bbclass/make-mod-scripts: inhibit default dependencies mark.yang
2026-07-08 2:28 ` [OE-core][PATCH 2/3] kernel-yocto: export CLANG_FLAGS for the kconfiglib config audit mark.yang
2026-07-08 2:28 ` [OE-core][PATCH 3/3] kernel-arch: add KERNEL_TOOLCHAIN for building the kernel with clang mark.yang
2026-07-08 2:37 ` [OE-core][PATCH 0/3] kernel: make the kernel toolchain switchable to clang Bruce Ashfield
2026-07-08 2:44 ` mark.yang [this message]
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=400669.1783478673234550269@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.