Bug ID | 1202195 |
---|---|
Summary | bpftool fails with latest binutils release |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Basesystem |
Assignee | screening-team-bugs@suse.de |
Reporter | martin.liska@suse.com |
QA Contact | qa-bugs@suse.de |
CC | jslaby@suse.com |
Found By | --- |
Blocker | --- |
Fails due to: [ 92s] jit_disasm.c:102:17: error: too few arguments to function 'init_disassemble_info' [ 92s] 102 | init_disassemble_info(&info, stdout, [ 92s] | ^~~~~~~~~~~~~~~~~~~~~ [ 92s] In file included from jit_disasm.c:23: [ 92s] /usr/include/dis-asm.h:472:13: note: declared here [ 92s] 472 | extern void init_disassemble_info (struct disassemble_info *dinfo, void *stream, [ 92s] | ^~~~~~~~~~~~~~~~~~~~~ [ 92s] jit_disasm.c:105:17: error: too few arguments to function 'init_disassemble_info' [ 92s] 105 | init_disassemble_info(&info, stdout, [ 92s] | ^~~~~~~~~~~~~~~~~~~~~ [ 92s] /usr/include/dis-asm.h:472:13: note: declared here [ 92s] 472 | extern void init_disassemble_info (struct disassemble_info *dinfo, void *stream, [ 92s] | ^~~~~~~~~~~~~~~~~~~~~ [ 92s] make: *** [Makefile:222: jit_disasm.o] Error 1 [ 92s] make: *** Waiting for unfinished jobs.... which is caused by an API change and Linux master addresses that with: 1e1613f64cc8 tools bpftool: Don't display disassembler-four-args feature test 600b7b26c07a tools bpftool: Fix compilation error with new binutils bab211f637dc tools bpf_jit_disasm: Don't display disassembler-four-args feature test 96ed066054ab tools bpf_jit_disasm: Fix compilation error with new binutils 83aa0120487e tools perf: Fix compilation error with new binutils a45b3d692623 tools include: add dis-asm-compat.h to handle version differences 516ddaadb424 tools build: Don't display disassembler-four-args feature test cfd59ca91467 tools build: Add feature test for init_disassemble_info API changes Can we expect these being backported to 5.19.1 or should we take them to our kernels-source tree?