Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Tue, 14 Jul 2020 11:19:47 +0200 | Subject | Re: linux-next: build failure after merge of the bpf-next tree |
| |
Hi Jiri,
On Tue, Jul 14, 2020 at 10:33 AM Jiri Olsa <jolsa@redhat.com> wrote: > On Tue, Jul 14, 2020 at 08:16:54AM +0200, Jiri Olsa wrote: > > On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote: > > > After merging the bpf-next tree, today's linux-next build (arm > > > multi_v7_defconfig) failed like this: > > > > > > tmp/ccsqpVCY.s: Assembler messages: > > > tmp/ccsqpVCY.s:78: Error: unrecognized symbol type "" > > > tmp/ccsqpVCY.s:91: Error: unrecognized symbol type "" > > > > > > I don't know what has caused this (I guess maybe the resolve_btfids > > > branch). > > > > > > I have used the bpf-next tree from next-20200713 for today.
Bummer, didn't find this report before I had bisected this to c9a0f3b85e09dd16 ("bpf: Resolve BTF IDs in vmlinux image"), and investigated the root cause (@object) myself, as the failing file path (net/core/filter.o) was not mentioned...
> > ok, trying to reproduce > > damn crossbuilds.. change below fixes it for me, > will do some more testing and post it today
Thanks, this fixes my (cross)arm32 build, and the (cross)arm64 build keeps working, and everything boots, so Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |