From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: fix a clang deprecated-declarations compilation error
Date: Sun, 20 Feb 2022 00:50:08 +0000 [thread overview]
Message-ID: <164531820898.13036.943833614769953266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220217194005.2765348-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 17 Feb 2022 11:40:05 -0800 you wrote:
> Build the kernel and selftest with clang compiler with LLVM=1,
> make -j LLVM=1
> make -C tools/testing/selftests/bpf -j LLVM=1
>
> I hit the following selftests/bpf compilation error:
> In file included from test_cpp.cpp:3:
> /.../tools/testing/selftests/bpf/tools/include/bpf/libbpf.h:73:8:
> error: 'relaxed_core_relocs' is deprecated: libbpf v0.6+: field has no effect [-Werror,-Wdeprecated-declarations]
> struct bpf_object_open_opts {
> ^
> test_cpp.cpp:56:2: note: in implicit move constructor for 'bpf_object_open_opts' first required here
> LIBBPF_OPTS(bpf_object_open_opts, opts);
> ^
> /.../tools/testing/selftests/bpf/tools/include/bpf/libbpf_common.h:77:3: note: expanded from macro 'LIBBPF_OPTS'
> (struct TYPE) { \
> ^
> /.../tools/testing/selftests/bpf/tools/include/bpf/libbpf.h:90:2: note: 'relaxed_core_relocs' has been explicitly marked deprecated here
> LIBBPF_DEPRECATED_SINCE(0, 6, "field has no effect")
> ^
> /.../tools/testing/selftests/bpf/tools/include/bpf/libbpf_common.h:24:4: note: expanded from macro 'LIBBPF_DEPRECATED_SINCE'
> (LIBBPF_DEPRECATED("libbpf v" # major "." # minor "+: " msg))
> ^
> /.../tools/testing/selftests/bpf/tools/include/bpf/libbpf_common.h:19:47: note: expanded from macro 'LIBBPF_DEPRECATED'
> #define LIBBPF_DEPRECATED(msg) __attribute__((deprecated(msg)))
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: fix a clang deprecated-declarations compilation error
https://git.kernel.org/bpf/bpf-next/c/a33c0c792d0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-20 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 19:40 [PATCH bpf-next] selftests/bpf: fix a clang deprecated-declarations compilation error Yonghong Song
2022-02-17 21:59 ` Andrii Nakryiko
2022-02-17 23:55 ` Yonghong Song
2022-02-20 0:50 ` patchwork-bot+netdevbpf [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=164531820898.13036.943833614769953266.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=yhs@fb.com \
/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