From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
acme@kernel.org, open list <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Leo Yan <leo.yan@linaro.org>
Cc: lkft-triage@lists.linaro.org
Subject: Linux-next: 20191022: perf: bpf_helpers_doc.py: not found
Date: Tue, 22 Oct 2019 21:04:04 +0530 [thread overview]
Message-ID: <CA+G9fYvWdkmmkrq7hvADZ-1qnUNEwRULoTPfOQDnu1aZW8cDEA@mail.gmail.com> (raw)
We have noticed perf (OE recipe) build failure on linux next 20191022.
do you see this failure ?
/bin/sh: 1: perf/1.0-r9/perf-1.0/scripts/bpf_helpers_doc.py: not found
Makefile:184: recipe for target 'bpf_helper_defs.h' failed
make[3]: *** [bpf_helper_defs.h] Error 127
make[3]: *** Deleting file 'bpf_helper_defs.h'
Makefile.perf:765: recipe for target 'perf/1.0-r9/perf-1.0/libbpf.a' failed
make[2]: *** [perf/1.0-r9/perf-1.0/libbpf.a] Error 2
Metadata:
------------------------------------------------------------------------
kernel: 5.4.0-rc4
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git branch: master
git commit: a722f75b2923b4fd44c17e7255e822ac48fe85f0
git describe: next-20191022
Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191022
Full build log:
https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=hikey,label=docker-lkft/631/consoleText
- Naresh
next reply other threads:[~2019-10-22 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 15:34 Naresh Kamboju [this message]
2019-10-23 2:41 ` Linux-next: 20191022: perf: bpf_helpers_doc.py: not found Leo Yan
2019-10-24 18:05 ` Daniel Díaz
2019-10-24 22:14 ` linux-next: bad merge resolution in the tip tree (Was: Linux-next: 20191022: perf: bpf_helpers_doc.py: not found) Stephen Rothwell
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=CA+G9fYvWdkmmkrq7hvADZ-1qnUNEwRULoTPfOQDnu1aZW8cDEA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkft-triage@lists.linaro.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;
as well as URLs for NNTP newsgroup(s).