From: Nathan Chancellor <nathan@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
"Borislav Petkov (AMD)" <bp@alien8.de>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/build: Do not allow X86_NATIVE_CPU to be enabled when compile testing
Date: Wed, 18 Nov 2026 21:17:17 -0700 [thread overview]
Message-ID: <20261119041717.GB1218811@ax162> (raw)
In-Reply-To: <20261118090035.15ced20c@pumpkin>
On Wed, Nov 18, 2026 at 09:00:35AM +0000, David Laight wrote:
> On Wed, 18 Nov 2026 00:28:48 -0700
> Nathan Chancellor <nathan@kernel.org> wrote:
> > $ make ARCH=... LLVM=1
> >
> > is generally all you need to do nowadays.
> >
>
> That requires that you also get the correct clang on $PATH.
> I'm sure I remember that not being as easy as it might seem.
Since
e9c281928c24 ("kbuild: Make $(LLVM) more flexible")
in 5.18, you can pass a full prefix to clang, which can help ensure you
are using the right toolchain since the build will error if you do not
point it to the right path:
$ make -skj"$(nproc)" ARCH=arm64 LLVM=/doesnt/exist/bin/ mrproper defconfig
make[3]: /doesnt/exist/bin/clang: No such file or directory
make[3]: /doesnt/exist/bin/clang: No such file or directory
/bin/sh: line 1: /doesnt/exist/bin/clang: No such file or directory
make[4]: *** [scripts/Makefile.host:114: scripts/basic/fixdep] Error 127
I use that when I am building with the kernel.org toolchains because
they live on disk in my home folder then I have clang tip in my path
that I can use with just LLVM=1.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-11-19 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 6:05 tip-bot2 for Nathan Chancellor
2026-11-16 9:40 ` Ingo Molnar
2026-11-16 13:01 ` Nathan Chancellor
2026-11-16 15:48 ` Linus Torvalds
2026-11-16 15:53 ` Linus Torvalds
2026-11-16 20:45 ` Nathan Chancellor
2026-11-19 3:16 ` Borislav Petkov
2026-11-19 4:12 ` Nathan Chancellor
2026-11-19 5:19 ` Borislav Petkov
2026-11-16 22:36 ` David Laight
2026-11-18 7:28 ` Nathan Chancellor
2026-11-18 9:00 ` David Laight
2026-11-19 4:17 ` Nathan Chancellor [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=20261119041717.GB1218811@ax162 \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®