From: Mark Brown <broonie@kernel.org>
To: Yonghong Song <yonghong.song@linux.dev>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
KBuild Mailing List <linux-kbuild@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the kbuild tree
Date: Mon, 16 Mar 2026 14:18:45 +0000 [thread overview]
Message-ID: <abgRRX3PH9IaExi8@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Hi all,
After merging the kbuild tree, today's linux-next build (arm64 perf)
failed like this:
Auto-detecting system features:
... libdw: [ on ]
... glibc: [ on ]
... libelf: [ on ]
... libnuma: [ on ]
... numa_num_possible_cpus: [ on ]
... libpython: [ on ]
... libcapstone: [ on ]
... llvm-perf: [ on ]
... zlib: [ on ]
... lzma: [ on ]
... bpf: [ on ]
... libaio: [ on ]
... libzstd: [ on ]
... libopenssl: [ on ]
... rust: [ on ]
Makefile:2254: *** extraneous 'endif'. Stop.
Makefile:2254: *** extraneous 'endif'. Stop.
PERF_VERSION = .gbc1f864a1976
52.34user 4.91system 0:56.88elapsed 100%CPU (0avgtext+0avgdata 140840maxresident)k
0inputs+0outputs (0major+1379795minor)pagefaults 0swaps
Building: arm64 allnoconfig
Makefile:2254: *** extraneous 'endif'. Stop.
Presumably caused by commit
6a76b3c06a1d3 (kbuild: Reduce the number of compiler-generated suffixes for clang thin-lto build)
though I don't immediately see how. I have used the version from
next-20260313 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-16 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 14:18 Mark Brown [this message]
2026-03-16 16:02 ` linux-next: build failure after merge of the kbuild tree Nicolas Schier
2026-03-16 16:16 ` Yonghong Song
2026-03-16 17:42 ` Mark Brown
2026-03-16 17:56 ` Nicolas Schier
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 4:01 Stephen Rothwell
2025-08-18 4:27 ` Nathan Chancellor
2016-09-15 6:08 Stephen Rothwell
2016-09-22 12:52 ` Michal Marek
[not found] <20110420082514.a9ec4d68.sfr@canb.auug.org.au>
2011-04-20 13:50 ` Michal Marek
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=abgRRX3PH9IaExi8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=yonghong.song@linux.dev \
/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