From: Sasha Levin <sashal@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
irogers@google.com
Subject: Re: [Regression in 6.19-rc6] Build breakage after commit 436326bc525d
Date: Tue, 20 Jan 2026 14:58:06 -0500 [thread overview]
Message-ID: <aW_eTgksTr1P2Gh1@laps> (raw)
In-Reply-To: <CAJZ5v0i6Uw0+L5SY3QW+py82uEVktNWcHGHf=Za96mQpN7X8Bw@mail.gmail.com>
On Tue, Jan 20, 2026 at 07:29:58PM +0100, Rafael J. Wysocki wrote:
>On Tue, Jan 20, 2026 at 6:40 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> On Tue, Jan 20, 2026 at 11:28:32AM +0100, Peter Zijlstra wrote:
>> >On Mon, Jan 19, 2026 at 09:19:31PM +0100, Rafael J. Wysocki wrote:
>> >> Hi Sasha,
>> >>
>> >> Commit 436326bc525d ("objtool: fix build failure due to missing
>> >> libopcodes check") breaks kernel build for me.
>> >>
>> >> Here's what I get when I try to build the kernel after that commit:
>> >>
>> >> LD /scratch/rafael/work/build/xps13/tools/objtool/objtool-in.o
>> >> LINK /scratch/rafael/work/build/xps13/tools/objtool/objtool
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
>> >> in function `print_operands':
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:3945:(.text+0x6317):
>> >> undefined reference to `xmalloc'
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:3992:(.text+0x6723):
>> >> undefined reference to `_sch_istable'
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
>> >> in function `print_insn_aarch64':
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:4559:(.text+0x6b1e):
>> >> undefined reference to `bfd_get_bits'
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
>> >> in function `parse_aarch64_dis_option':
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:103:(.text+0x6dea):
>> >> undefined reference to `_bfd_error_handler'
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-opc.o):
>> >> in function `init_insn_sequence':
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-opc.c:5561:(.text+0x5c06):
>> >> undefined reference to `xcalloc'
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
>> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(disassemble.o):
>> >> in function `remove_whitespace_and_extra_commas':
>> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/disassemble.c:801:(.text+0x346):
>> >> undefined reference to `_sch_istable'
>> >> ...
>> >>
>> >> (many more similar messages skipped).
>> >>
>> >> Reverting commit 436326bc525d makes the problem go away.
>>
>> Thanks for the report Rafael!
>>
>> Could you confirm that you're linking against static libraries? I haven't
>> tested that scenario.
>
>How do I check that?
What do you get running the below?
ls /usr/lib/*/libopcodes*
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-01-20 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 20:19 [Regression in 6.19-rc6] Build breakage after commit 436326bc525d Rafael J. Wysocki
2026-01-20 10:28 ` Peter Zijlstra
2026-01-20 17:40 ` Sasha Levin
2026-01-20 18:29 ` Rafael J. Wysocki
2026-01-20 19:58 ` Sasha Levin [this message]
2026-01-20 20:04 ` Rafael J. Wysocki
2026-01-20 20:22 ` Sasha Levin
2026-01-20 21:33 ` Rafael J. Wysocki
2026-01-21 1:18 ` Sasha Levin
2026-01-21 5:29 ` Josh Poimboeuf
2026-01-21 12:06 ` Sasha Levin
2026-01-21 16:25 ` [PATCH] objtool: fix libopcodes linking with static libraries Sasha Levin
2026-01-21 19:08 ` Rafael J. Wysocki
2026-01-21 19:25 ` Peter Zijlstra
2026-01-21 19:28 ` [tip: objtool/urgent] objtool: Fix " tip-bot2 for Sasha Levin
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=aW_eTgksTr1P2Gh1@laps \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=x86@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