From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: bpf@vger.kernel.org, Will Deacon <will@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: tools/bpf: Compilation issue on powerpc: unknown type name '__vector128'
Date: Sat, 24 Oct 2020 11:23:19 +0300 [thread overview]
Message-ID: <20201024082319.GA24131@altlinux.org> (raw)
In-Reply-To: <20201023230641.xomukhg3zrhtuxez@altlinux.org>
Hi,
On Sat, Oct 24, 2020 at 02:06:41AM +0300, Vitaly Chikunov wrote:
> Hi,
>
> Commit f143c11bb7b9 ("tools: bpf: Use local copy of headers including
> uapi/linux/filter.h") introduces compilation issue on powerpc:
>
> builder@powerpc64le:~/linux$ make -C tools/bpf V=1
> make: Entering directory '/usr/src/linux/tools/bpf'
> gcc -Wall -O2 -D__EXPORTED_HEADERS__ -I/usr/src/linux/tools/include/uapi -I/usr/src/linux/tools/include -DDISASM_FOUR_ARGS_SIGNATURE -c -o bpf_dbg.o /usr/src/linux/tools/bpf/bpf_dbg.c
> In file included from /usr/include/asm/sigcontext.h:14,
> from /usr/include/bits/sigcontext.h:30,
> from /usr/include/signal.h:291,
> from /usr/src/linux/tools/bpf/bpf_dbg.c:51:
> /usr/include/asm/elf.h:160:9: error: unknown type name '__vector128'
> 160 | typedef __vector128 elf_vrreg_t;
> | ^~~~~~~~~~~
> make: *** [Makefile:67: bpf_dbg.o] Error 1
> make: Leaving directory '/usr/src/linux/tools/bpf'
__vector128 is defined in arch/powerpc/include/uapi/asm/types.h;
while include/uapi/linux/types.h does #include <asm/types.h>,
tools/include/uapi/linux/types.h doesn't, resulting to this
compilation error.
--
ldv
next prev parent reply other threads:[~2020-10-24 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 23:06 tools/bpf: Compilation issue on powerpc: unknown type name '__vector128' Vitaly Chikunov
2020-10-24 8:23 ` Dmitry V. Levin [this message]
2020-10-24 20:30 ` Vitaly Chikunov
2020-10-26 4:45 ` Michael Ellerman
2020-10-26 8:46 ` Will Deacon
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=20201024082319.GA24131@altlinux.org \
--to=ldv@altlinux.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=vt@altlinux.org \
--cc=will@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