public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
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


  reply	other threads:[~2026-03-16 16:16 UTC|newest]

Thread overview: 96+ 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
2025-07-30  6:12 Stephen Rothwell
2025-08-04  1:25 ` Stephen Rothwell
2025-08-04  7:09   ` Alexey Gladkov
2025-08-04 22:17     ` Stephen Rothwell
2025-08-05  3:33       ` Stephen Rothwell
2025-08-12 21:51         ` Alexey Gladkov
2025-06-03  6:39 Stephen Rothwell
2025-03-23 23:30 Stephen Rothwell
2025-03-24 13:52 ` Jeff Johnson
2025-03-24 17:37   ` Arnd Bergmann
2025-03-24 17:40     ` Jeff Johnson
2025-03-26 23:16 ` Stephen Rothwell
2025-03-27  0:20   ` Jeff Johnson
2025-03-27 10:13     ` Alessandro Carminati
2024-09-11  0:18 Stephen Rothwell
2024-09-11  9:38 ` Masahiro Yamada
2024-09-11 13:20   ` Kris Van Hees
2024-09-12  1:49     ` Masahiro Yamada
2022-10-14  1:42 Stephen Rothwell
2022-10-14 13:31 ` Masahiro Yamada
2022-10-12 22:17 Stephen Rothwell
2022-10-12 22:34 ` Masahiro Yamada
2022-10-12 23:51   ` Stephen Rothwell
2022-09-08 23:00 Stephen Rothwell
2022-09-09  5:10 ` Masahiro Yamada
2022-09-09  5:24   ` Stephen Rothwell
2022-09-09  6:13     ` Stephen Rothwell
2022-09-09  6:48       ` Masahiro Yamada
2022-09-09  7:49         ` Stephen Rothwell
     [not found]           ` <CAK7LNARiW66Hk5JJgRYb-edkb6sgTWPbNr1iETkq-RASCo-YkA@mail.gmail.com>
2022-09-11 23:55             ` Stephen Rothwell
2022-09-12  5:06               ` Masahiro Yamada
2022-09-12  7:43                 ` Stephen Rothwell
2022-09-09  8:26         ` Stephen Rothwell
2022-09-08  0:06 Stephen Rothwell
2022-09-08  4:14 ` Masahiro Yamada
2022-09-07 12:34 Stephen Rothwell
2022-09-07 13:49 ` Masahiro Yamada
2022-05-23 10:59 Stephen Rothwell
2022-05-23 15:59 ` Masahiro Yamada
2021-08-26  9:13 Stephen Rothwell
2021-08-27  0:52 ` Masahiro Yamada
2021-08-27  1:50   ` Stephen Rothwell
2021-08-27  2:49     ` Masahiro Yamada
2021-02-21 21:33 Stephen Rothwell
2021-02-21 23:21 ` Masahiro Yamada
2020-07-07  7:07 Stephen Rothwell
2020-07-13  1:56 ` Stephen Rothwell
2020-07-13  7:52   ` Masahiro Yamada
2020-04-06  2:34 Stephen Rothwell
2020-04-07  4:41 ` Masahiro Yamada
2020-03-10 22:53 Stephen Rothwell
2020-03-11  4:22 ` Masahiro Yamada
2019-07-16  4:31 Stephen Rothwell
2019-07-16  4:59 ` Masahiro Yamada
2019-07-16  6:42   ` Stephen Rothwell
2019-07-05  8:31 Stephen Rothwell
2019-07-06  0:05 ` Michael Kelley
2019-07-06  0:58   ` Masahiro Yamada
2019-05-05 23:46 Stephen Rothwell
2019-05-05 23:35 Stephen Rothwell
2019-05-05 22:40 Stephen Rothwell
2018-08-22 22:35 Stephen Rothwell
2018-08-23  9:03 ` Masahiro Yamada
2018-05-30  1:29 Stephen Rothwell
2018-05-30  1:44 ` Masahiro Yamada
2018-05-15  5:50 Stephen Rothwell
2018-05-16  6:01 ` Masahiro Yamada
2018-05-16  7:26   ` Stephen Rothwell
2018-05-17 13:45     ` Masahiro Yamada
2018-03-28 21:58 Stephen Rothwell
2018-03-29  1:59 ` Masahiro Yamada
2016-09-15  6:08 Stephen Rothwell
2016-09-22 12:52 ` Michal Marek
2016-07-28  2:08 Stephen Rothwell
2016-07-28  2:40 ` Michael Ellerman
2016-03-15 23:58 Stephen Rothwell
2016-03-16  7:53 ` Daniel Wagner
2016-03-16  7:56   ` Michal Marek
2016-03-16 11:29     ` Stephen Rothwell
2016-03-16 11:31       ` Michal Marek
2013-02-24 23:56 Stephen Rothwell
2013-02-25 10:28 ` Michal Marek
2013-02-25 10:58   ` Stephen Rothwell
2013-02-25 11:02     ` Stephen Rothwell
2013-02-25 11:36     ` Michal Marek
2011-04-19 22:25 Stephen Rothwell
2011-04-19 22:30 ` Stephen Rothwell
2011-04-20 13:50 ` Michal Marek
2010-03-11  5:15 Stephen Rothwell

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