public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Nicolas Schier" <nsc@kernel.org>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"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: Sun, 17 Aug 2025 21:27:01 -0700	[thread overview]
Message-ID: <20250818042701.GA2367466@ax162> (raw)
In-Reply-To: <20250818140143.61b8c466@canb.auug.org.au>

On Mon, Aug 18, 2025 at 02:01:43PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the kbuild tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> /usr/bin/ld: /usr/lib/gcc/powerpc64le-linux-gnu/14/../../../powerpc64le-linux-gnu/libgcc_s.so.1: error adding symbols: file in wrong format
> collect2: error: ld returned 1 exit status
> make[5]: *** [scripts/Makefile.userprogs:29: samples/pfsm/pfsm-wakeup] Error 1
> make[5]: Target 'samples/pfsm/' not remade because of errors.
> 
> an so on for lots more ...
> 
> Caused by commit
> 
>   478494044bb4 ("kbuild: userprogs: also inherit byte order and ABI from kernel")
> 
> I have reverted that commit for today.
> 
> Build was done on ppc64le, POWER9
> 
> $ gcc --version
> gcc (Debian 14.2.0-19) 14.2.0
> $ ld --version
> GNU ld (GNU Binutils for Debian) 2.44
> 
> CONFIG_VDSO32=y
> CONFIG_CPU_BIG_ENDIAN=y
> # CONFIG_CPU_LITTLE_ENDIAN is not set
> CONFIG_PPC64_ELF_ABI_V2=y
> CONFIG_CC_HAS_ELFV2=y
> CONFIG_CC_HAS_PREFIXED=y
> CONFIG_CC_HAS_PCREL=y
> CONFIG_64BIT=y

Thanks a lot for the report. Now that I am looking at the test for
CONFIG_CC_CAN_LINK, I am not sure that change is fully correct because
those additional flags are not accounted for in that test. We would need
something like this but if I understand correctly, the filtering of the
flags would need to happen much earlier that it currently does. I have
dropped that change from kbuild-next for now. Thomas, please investigate
and send me a new patch.

Cheers,
Nathan

diff --git a/init/Kconfig b/init/Kconfig
index 836320251219..ab8aa6ab8aa4 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -84,8 +84,8 @@ config RUSTC_LLVM_VERSION
 
 config CC_CAN_LINK
 	bool
-	default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m64-flag)) if 64BIT
-	default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(USERCFLAGS) $(USERLDFLAGS) $(m32-flag))
+	default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(KBUILD_USERCFLAGS) $(KBUILD_USERLDFLAGS) $(m64-flag)) if 64BIT
+	default $(success,$(srctree)/scripts/cc-can-link.sh $(CC) $(CLANG_FLAGS) $(KBUILD_USERCFLAGS) $(KBUILD_USERLDFLAGS) $(m32-flag))
 
 # Fixed in GCC 14, 13.3, 12.4 and 11.5
 # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921

  reply	other threads:[~2025-08-18  4:27 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  4:01 linux-next: build failure after merge of the kbuild tree Stephen Rothwell
2025-08-18  4:27 ` Nathan Chancellor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-16 14:18 Mark Brown
2026-03-16 16:02 ` Nicolas Schier
2026-03-16 16:16   ` Yonghong Song
2026-03-16 17:42   ` Mark Brown
2026-03-16 17:56     ` Nicolas Schier
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=20250818042701.GA2367466@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nsc@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=thomas.weissschuh@linutronix.de \
    /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