From: Lina Wang <lina.wang@mediatek.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Maciej enczykowski <maze@google.com>, <netdev@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <lkp@intel.com>,
<rong.a.chen@intel.com>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] selftests net: fix bpf build error
Date: Wed, 1 Jun 2022 15:08:44 +0800 [thread overview]
Message-ID: <20220601070844.10515-1-lina.wang@mediatek.com> (raw)
In-Reply-To: <9c462ffc-f2c0-f542-4e61-251571da8c22@iogearbox.net>
On Wed, 2022-06-01 at 01:01 +0200, Daniel Borkmann wrote:
> On 5/30/22 8:21 AM, Lina Wang wrote:
> clang -O2 -target bpf -c bpf/nat6to4.c -I../../bpf -I../../../../lib
> -I../../../../../usr/include/ -o
> /root/daniel/bpf/tools/testing/selftests/net/bpf/nat6to4.o
> In file included from bpf/nat6to4.c:27:
> In file included from /usr/include/linux/bpf.h:11:
> /usr/include/linux/types.h:5:10: fatal error: 'asm/types.h' file not
> found
> #include <asm/types.h>
> ^~~~~~~~~~~~~
> 1 error generated.
maybe your pc is ubuntu or Debian, you should apt-get install gcc-multilib,
guys on the internet meets the same problem when build libbpf related, just
install gcc-multilib package
> Could we reuse the build infra from tools/testing/selftests/bpf/ for nat6to4.c?
We discussed it before, please refer to https://patchwork.kernel.org/project/netdevbpf/patch/20220407084727.10241-1-lina.wang@mediatek.com/
Thanks!
prev parent reply other threads:[~2022-06-01 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:21 Lina Wang
2022-05-31 22:27 ` Song Liu
2022-05-31 23:01 ` Daniel Borkmann
2022-06-01 7:08 ` Lina Wang [this message]
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=20220601070844.10515-1-lina.wang@mediatek.com \
--to=lina.wang@mediatek.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=pabeni@redhat.com \
--cc=rong.a.chen@intel.com \
--cc=shuah@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
all inboxes | Powered by JetHome®