Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: bpf <bpf@vger.kernel.org>, Netdev <netdev@vger.kernel.org>,
"Alexei Starovoitov" <ast@fb.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Kernel Team" <kernel-team@fb.com>,
"Andrii Nakryiko" <andriin@fb.com>,
lkft-triage@lists.linaro.org,
"Daniel Díaz" <daniel.diaz@linaro.org>
Subject: Re: expects argument of type 'size_t', but argument 5 has type 'Elf64_Xword
Date: Tue, 25 Aug 2020 20:18:21 -0700 [thread overview]
Message-ID: <CAEf4BzZO_NnBSRe--V1GAu=ZeennVpZDOAzcE6e+0V=coVuXcw@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYvWkGp9p95DQ5T87GDBmUMecEYBZC0TYHmfwHysanQ7zA@mail.gmail.com>
On Mon, Aug 24, 2020 at 2:00 AM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
>
> while building perf with gcc 7.3.0 on linux next this warning/error is found.
>
> In file included from libbpf.c:55:0:
> libbpf.c: In function 'bpf_object__elf_collect':
> libbpf_internal.h:74:22: error: format '%zu' expects argument of type
> 'size_t', but argument 5 has type 'Elf64_Xword {aka long long unsigned
> int}' [-Werror=format=]
> libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__);
> cc1: all warnings being treated as errors
>
You left out the most useful part:
| libbpf.c:2826:4: note: in expansion of macro 'pr_info'
| pr_info("elf: skipping section(%d) %s (size %zu)\n", idx, name,
sh.sh_size);
| ^~~~~~~
| libbpf.c:2826:50: note: format string is defined here
| pr_info("elf: skipping section(%d) %s (size %zu)\n", idx, name,
sh.sh_size);
| ~~^
| %llu
But I fixed it as part of [0], thanks.
[0] https://patchwork.ozlabs.org/project/netdev/patch/20200826030922.2591203-1-andriin@fb.com/
> OE perf build long link,
> https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=am57xx-evm,label=docker-lkft/846/consoleText
>
> - Naresh
prev parent reply other threads:[~2020-08-26 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 9:00 Naresh Kamboju
2020-08-26 3:18 ` Andrii Nakryiko [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='CAEf4BzZO_NnBSRe--V1GAu=ZeennVpZDOAzcE6e+0V=coVuXcw@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--subject='Re: expects argument of type '\''size_t'\'', but argument 5 has type '\''Elf64_Xword' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).