From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>
Cc: 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, 04 Jul 2025 15:25:49 +0200 [thread overview]
Message-ID: <617201f8-1ad7-4403-b195-8c80d35ea30f@app.fastmail.com> (raw)
In-Reply-To: <8362b484-ea77-4825-8ccb-d5acad660102@oss.qualcomm.com>
On Mon, Jun 23, 2025, at 21:52, Jeff Johnson wrote:
> I've been using crosstools gcc 14.2.0.
>
> Today I saw that gcc 15.1.0 has been added to crosstools:
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/15.1.0/
>
> But when I try it I'm getting an error:
> LD vmlinux.o
> 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:
> invalid section alignment
> make[5]: *** [scripts/Makefile.vmlinux_o:72: vmlinux.o] Error 1
> make[5]: *** Deleting file 'vmlinux.o'
> make[5]: Target '__default' not remade because of errors.
> make[4]: *** [Makefile:1217: vmlinux_o] Error 2
> make[4]: Target 'all' not remade because of errors.
> make[3]: *** [debian/rules:80: build-arch] Error 2
> make[3]: Target 'binary' not remade because of errors.
> dpkg-buildpackage: error: make -f debian/rules binary subprocess
> returned exit status 2
> make[2]: *** [scripts/Makefile.package:126: bindeb-pkg] Error 2
> make[1]: ***
> [/local/mnt/workspace/jjohnson/kernel/laptop-debug/Makefile:1635:
> bindeb-pkg] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> make: Target 'bindeb-pkg' not remade because of errors.
>
> This is with a simple x86 make C=1 W=1 -j8 bindeb-pkg
>
> Any thoughts?
Hi Jeff,
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.
My best guess is that this is an objtool issue, as new compiler
versions tend to trigger new cases that were not previously covered
in objtool.
Arnd
next parent reply other threads:[~2025-07-04 13:26 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 [this message]
2025-07-24 10:44 ` Mark Rutland
2025-07-24 15:37 ` Arnd Bergmann
2025-07-25 9:08 ` Mark Rutland
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=617201f8-1ad7-4403-b195-8c80d35ea30f@app.fastmail.com \
--to=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®