mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: build failure with crosstools gcc 15.1.0
Date: Fri, 25 Jul 2025 10:08:23 +0100	[thread overview]
Message-ID: <aINJh-WFKHhxZ3fW@J2N7QTR9R3> (raw)
In-Reply-To: <b2feb2ec-9e69-4ab4-b75a-6c7f287c763d@app.fastmail.com>

On Thu, Jul 24, 2025 at 05:37:11PM +0200, Arnd Bergmann wrote:
> On Thu, Jul 24, 2025, at 12:44, Mark Rutland wrote:
> > On Fri, Jul 04, 2025 at 03:25:49PM +0200, Arnd Bergmann wrote:
> >> On Mon, Jun 23, 2025, at 21:52, Jeff Johnson wrote:
> >> > vmlinux.o: warning: objtool: ncsi_process_next_channel() falls through 
> >> > to next function ncsi_channel_monitor.cold()
> >> > vmlinux.o: error: objtool [elf.c:1360]: elf_write: elf_update failed: 
> >> 
> >> Sorry for the late reply, have you figured it out in the meantime?
> >> 
> >> I couldn't immediately reproduce it, so it may already be fixed
> >> in linux-next.
> >
> > $ git clean -fdx
> > $ usekorg 15.1.0 make ARCH=x86_64 CROSS_COMPILE=x86_64-linux- defconfig
> > $ usekorg 15.1.0 make ARCH=x86_64 CROSS_COMPILE=x86_64-linux- -j56
> 
> This is very close to what I use. I assume you are also on an arm64
> host here?

Nope, this was on an x86-64 host running Debian 11.10.

I *DON'T* see this when building on an arm64 host running Debain 12.11,
using the (arm64 builds of) the GCC 15.1.0 binaries from kernel.org.

That suggests this is down to something on the build host. Given that
the failure is seen at a call to elf_update() (which is part of libelf):

	/* Write all changes to the file. */
	if (elf_update(elf->elf, ELF_C_WRITE) < 0) {
		ERROR_ELF("elf_update");
		return -1;
	}

... I suspect the version of libelf might have something to do with it.

The x86 host has libelf-dev 0.183-1 whereas the arm64 host has
libelf-dev 0.188-2.1, so maybe there's something added or fixed between
those versions.

Otherwise, looking at the resulting .config files, the only differences
are:

* The x86 host has:

  CONFIG_PAHOLE_VERSION=120
  CONFIG_CC_HAS_MARCH_NATIVE=y
  # CONFIG_X86_NATIVE_CPU is not set

* The arm64 host has:

  CONFIG_PAHOLE_VERSION=124

... and otherwise everything else is the same.

AFAICT, pahole shouldn't affect the build since none of the BTF options
are selected.

Mark.

  reply	other threads:[~2025-07-25  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8362b484-ea77-4825-8ccb-d5acad660102@oss.qualcomm.com>
2025-07-04 13:25 ` Arnd Bergmann
2025-07-24 10:44   ` Mark Rutland
2025-07-24 15:37     ` Arnd Bergmann
2025-07-25  9:08       ` Mark Rutland [this message]
2025-07-25 15:19         ` Jeff Johnson

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=aINJh-WFKHhxZ3fW@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=arnd@arndb.de \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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®