From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
perf-users <perf-users@linaro.org>,
lkft-triage@lists.linaro.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
NeilBrown <neilb@suse.de>,
tanu235m@gmail.com, Matthew Wilcox <willy@infradead.org>,
Thierry Reding <thierry.reding@gmail.com>,
mgorman@techsingularity.net,
Andrew Morton <akpm@linux-foundation.org>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Alan Maguire <alan.maguire@oracle.com>,
Dave Marchevsky <davemarchevsky@fb.com>
Subject: Re: [next] perf build failures: libbpf.c:10946:50: error: format '%li' expects argument of type 'long int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'} [-Werror=format=]
Date: Thu, 7 Apr 2022 22:23:41 +1000 [thread overview]
Message-ID: <20220407222341.626d8377@canb.auug.org.au> (raw)
In-Reply-To: <CA+G9fYvdH87k2sSy6g3ehkqE8W94wdg-ww9-wS_t9w48Sp55PQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
Hi Naresh,
On Thu, 7 Apr 2022 15:46:53 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> perf build errors on i386 [1] on Linux next-20220407 [2]
>
> usdt.c:1181:5: error: "__x86_64__" is not defined, evaluates to 0
> [-Werror=undef]
> 1181 | #if __x86_64__
> | ^~~~~~~~~~
> usdt.c:1196:5: error: "__x86_64__" is not defined, evaluates to 0
> [-Werror=undef]
> 1196 | #if __x86_64__
> | ^~~~~~~~~~
> cc1: all warnings being treated as errors
Caused by commit
4c59e584d158 ("libbpf: Add x86-specific USDT arg spec parsing logic")
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/util/values.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/tests/backward-ring-buffer.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/tests/sdt.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/tests/is_printable_array.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/util/debug.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/util/fncache.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/tests/bitmap.o
> CC /home/tuxbuild/.cache/tuxmake/builds/1/build/util/machine.o
> libbpf.c: In function 'attach_uprobe':
> libbpf.c:10946:50: error: format '%li' expects argument of type 'long
> int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'}
> [-Werror=format=]
> 10946 | n = sscanf(func_name, "%m[a-zA-Z0-9_.]+%li", &func, &offset);
> | ~~^ ~~~~~~~
> | | |
> | long int *
> size_t * {aka unsigned int *}
> | %i
> cc1: all warnings being treated as errors
Caused by commit
39f8dc43b7a0 ("libbpf: Add auto-attach for uprobes based on section name")
> metadata:
> git_ref: master
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: 2e9a9857569ec27e64d2ddd01294bbe3c736acb1
> git_describe: next-20220407
> kernel-config: https://builds.tuxbuild.com/27SL0lCnWoPP04Jn8zKQ5nEEX7i/config
> target_arch: i386
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
>
> [1] https://builds.tuxbuild.com/27SL0lCnWoPP04Jn8zKQ5nEEX7i/
> [2] https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/2302706510
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-07 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 10:16 [next] perf build failures: libbpf.c:10946:50: error: format '%li' expects argument of type 'long int *', but argument 4 has type 'size_t *' {aka 'unsigned int *'} [-Werror=format=] Naresh Kamboju
2022-04-07 12:23 ` Stephen Rothwell [this message]
2022-04-07 15:57 ` Andrii Nakryiko
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=20220407222341.626d8377@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=davemarchevsky@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@techsingularity.net \
--cc=naresh.kamboju@linaro.org \
--cc=neilb@suse.de \
--cc=perf-users@linaro.org \
--cc=tanu235m@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=willy@infradead.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