From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org,
Andrii Nakryiko <andrii@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [next-20220721] Build failure powerpc (tools/bpf)
Date: Thu, 28 Jul 2022 18:44:28 -0700 [thread overview]
Message-ID: <CAEf4BzZPaYzhH6zoJVMrOyJOPOcs19xUkmmw2y0uRFF5Z_eznA@mail.gmail.com> (raw)
In-Reply-To: <4A5CBF60-9590-417D-ADE7-7C6FDA8520DB@linux.ibm.com>
On Fri, Jul 22, 2022 at 12:04 AM Sachin Sant <sachinp@linux.ibm.com> wrote:
>
> next-20220721 build fails on IBM Power server with following error:
>
> libbpf.c: In function 'bpf_program__attach_ksyscall':
> libbpf.c:10130:45: error: '%s' directive argument is null [-Werror=format-truncation=]
> snprintf(func_name, sizeof(func_name), "__%s_sys_%s",
> ^~
> cc1: all warnings being treated as errors
> make[4]: *** [/home/linux-next/tools/build/Makefile.build:96: /home/linux-next/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o] Error 1
> make[3]: *** [Makefile:157: /home/linux-next/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2
> make[2]: *** [Makefile:55: /home/linux-next/tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2
> make[1]: *** [Makefile:76: bpf/resolve_btfids] Error 2
> make: *** [Makefile:1439: tools/bpf/resolve_btfids] Error 2
>
> next-20220719 was good. Git bisect points to following commit
>
> Commit 708ac5bea0ce
> libbpf: add ksyscall/kretsyscall sections support for syscall kprobes
>
>
This was addressed by [0], thanks for report!
[0] https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=64893e83f916
> Reverting this commit allows me to build the kernel.
>
> Have attached .config used for build.
>
> - Sachin
>
prev parent reply other threads:[~2022-07-29 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:04 [next-20220721] Build failure powerpc (tools/bpf) Sachin Sant
2022-07-29 1:44 ` 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=CAEf4BzZPaYzhH6zoJVMrOyJOPOcs19xUkmmw2y0uRFF5Z_eznA@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).