From: Rong Tao <rtoax@foxmail.com>
To: yonghong.song@linux.dev
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
martin.lau@linux.dev, mykolal@fb.com, olsajiri@gmail.com,
rongtao@cestc.cn, rtoax@foxmail.com, sdf@google.com,
shuah@kernel.org, song@kernel.org
Subject: Re: [PATCH bpf-next v5] selftests/bpf: trace_helpers.c: optimize kallsyms cache
Date: Mon, 21 Aug 2023 14:49:58 +0800 [thread overview]
Message-ID: <tencent_AA234615114B0D808474B2D42F9955A25F09@qq.com> (raw)
In-Reply-To: <c2f564a3-f942-d275-3ecb-b679aa0810ec@linux.dev>
tools/testing/selftests/bpf/ compile OK, however, samples/bpf/ compile failed.
>> tools/testing/selftests/bpf/trace_helpers.c:17:10:
>> fatal error: libbpf_internal.h: No such file or directory
>> 17 | #include "libbpf_internal.h"
>> | ^~~~~~~~~~~~~~~~~~~
>>
>> tools/testing/selftests/bpf/trace_helpers.c:17:10:
>> fatal error: bpf/libbpf_internal.h: No such file or directory
>> 17 | #include "bpf/libbpf_internal.h"
>> | ^~~~~~~~~~~~~~~~~~~~~~~
I just submit v6 [0], which apply libbpf_ensure_mem() and
TPROGS_CFLAGS += -I$(srctree)/tools/lib
to samples/bpf/Makefile, make sure, samples/bpf/Makefile could found
libbpf_internal.h.
Please review, thanks.
Rong Tao
[0] https://lore.kernel.org/lkml/tencent_4A09A36F883A06EA428A593497642AF8AF08@qq.com/
prev parent reply other threads:[~2023-08-21 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 5:03 Rong Tao
2023-08-17 8:21 ` Jiri Olsa
2023-08-18 1:39 ` Rong Tao
2023-08-18 12:20 ` Jiri Olsa
2023-08-18 15:36 ` Rong Tao
2023-08-18 17:50 ` Yonghong Song
2023-08-21 2:03 ` Rong Tao
2023-08-21 4:34 ` Yonghong Song
2023-08-21 6:49 ` Rong Tao [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=tencent_AA234615114B0D808474B2D42F9955A25F09@qq.com \
--to=rtoax@foxmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=olsajiri@gmail.com \
--cc=rongtao@cestc.cn \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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®