From: Yonghong Song <yonghong.song@linux.dev>
To: Nicolas Schier <nsc@kernel.org>, Mark Brown <broonie@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
KBuild Mailing List <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree
Date: Mon, 16 Mar 2026 09:16:26 -0700 [thread overview]
Message-ID: <6db3a2f6-d61c-42f1-9b9d-0aca021cc2d7@linux.dev> (raw)
In-Reply-To: <abgph5Gk1G8UgG2E@levanger>
On 3/16/26 9:02 AM, Nicolas Schier wrote:
> Hi Mark,
>
> On Mon, Mar 16, 2026 at 02:18:45PM +0000, Mark Brown wrote:
>> 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.
> thanks for the report. Unfortunately, I cannot reproduce that anyhow;
> but I pushed to kbuild/kbuild-for-next at 12:36 UTC, might that have
> been a bad point in time? Do you have your merge somewhere around where
> I can fetch it for investigation?
I guess it probably due to my bad suggestions (sorry I should have tested before
sending out).
else
CC_FLAGS_LTO := -flto=thin -fsplit-lto-unit
+if CONFIG_LTO_CLANG_THIN
+KBUILD_LDFLAGS += $(call ld-option,--lto-whole-program-visibility
-mllvm -always-rename-promoted-locals=false)
+endif
endifIt should be else
CC_FLAGS_LTO := -flto=thin -fsplit-lto-unit
+ifdef CONFIG_LTO_CLANG_THIN
+KBUILD_LDFLAGS += $(call ld-option,--lto-whole-program-visibility
-mllvm -always-rename-promoted-locals=false)
+endif
endif
>
> Kind regards,
> Nicolas
next prev parent reply other threads:[~2026-03-16 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 14:18 linux-next: build failure after merge of the kbuild tree Mark Brown
2026-03-16 16:02 ` Nicolas Schier
2026-03-16 16:16 ` Yonghong Song [this message]
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=6db3a2f6-d61c-42f1-9b9d-0aca021cc2d7@linux.dev \
--to=yonghong.song@linux.dev \
--cc=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 \
/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