[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc8b0c65-b74a-d924-4189-ff6359d1ebdc@iogearbox.net>
Date: Wed, 2 Sep 2020 23:51:26 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Andrii Nakryiko <andrii.nakryiko@...il.com>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
Cc: bpf <bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Jiri Olsa <jolsa@...hat.com>,
Vaidyanathan Srinivasan <svaidy@...ux.ibm.com>
Subject: Re: [PATCH] libbpf: Remove arch-specific include path in Makefile
On 9/2/20 10:58 PM, Andrii Nakryiko wrote:
> On Wed, Sep 2, 2020 at 1:43 AM Naveen N. Rao
> <naveen.n.rao@...ux.vnet.ibm.com> wrote:
>>
>> Ubuntu mainline builds for ppc64le are failing with the below error (*):
>> CALL /home/kernel/COD/linux/scripts/atomic/check-atomics.sh
>> DESCEND bpf/resolve_btfids
>>
>> Auto-detecting system features:
>> ... libelf: [ [32mon[m ]
>> ... zlib: [ [32mon[m ]
>> ... bpf: [ [31mOFF[m ]
>>
>> BPF API too old
>> make[6]: *** [Makefile:295: bpfdep] Error 1
>> make[5]: *** [Makefile:54: /home/kernel/COD/linux/debian/build/build-generic/tools/bpf/resolve_btfids//libbpf.a] Error 2
>> make[4]: *** [Makefile:71: bpf/resolve_btfids] Error 2
>> make[3]: *** [/home/kernel/COD/linux/Makefile:1890: tools/bpf/resolve_btfids] Error 2
>> make[2]: *** [/home/kernel/COD/linux/Makefile:335: __build_one_by_one] Error 2
>> make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic'
>> make[1]: *** [Makefile:185: __sub-make] Error 2
>> make[1]: Leaving directory '/home/kernel/COD/linux'
>>
>> resolve_btfids needs to be build as a host binary and it needs libbpf.
>> However, libbpf Makefile hardcodes an include path utilizing $(ARCH).
>> This results in mixing of cross-architecture headers resulting in a
>> build failure.
>>
>> The specific header include path doesn't seem necessary for a libbpf
>> build. Hence, remove the same.
>>
>> (*) https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc3/ppc64el/log
>>
>> Reported-by: Vaidyanathan Srinivasan <svaidy@...ux.ibm.com>
>> Signed-off-by: Naveen N. Rao <naveen.n.rao@...ux.vnet.ibm.com>
>> ---
>
> This seems to still build fine for me, so I seems fine. Not sure why
> that $(ARCH)/include/uapi path is there.
>
> Acked-by: Andrii Nakryiko <andriin@...com>
Same here, builds fine from my side too. Looks like this was from the very early days,
added in commit 1b76c13e4b36 ("bpf tools: Introduce 'bpf' library and add bpf feature
check"). Applied, thanks!
Powered by blists - more mailing lists