From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@redhat.com>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kbuild@vger.kernel.org,
Martin KaFai Lau <kafai@fb.com>
Subject: Re: [PATCHv2 bpf-next] kbuild: Unify options for BTF generation for vmlinux and modules
Date: Wed, 27 Oct 2021 22:57:08 +0800 [thread overview]
Message-ID: <202110272241.3Njacivm-lkp@intel.com> (raw)
In-Reply-To: <20211026212419.144077-1-jolsa@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3945 bytes --]
Hi Jiri,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Jiri-Olsa/kbuild-Unify-options-for-BTF-generation-for-vmlinux-and-modules/20211027-052639
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: openrisc-buildonly-randconfig-r001-20211027 (attached as .config)
compiler: or1k-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/cd9d0571d9b0204fb3c1badf41ca847ba840e40c
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jiri-Olsa/kbuild-Unify-options-for-BTF-generation-for-vmlinux-and-modules/20211027-052639
git checkout cd9d0571d9b0204fb3c1badf41ca847ba840e40c
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=openrisc SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
make[1]: *** [Makefile:1871: init] Error 2
make[1]: *** [Makefile:1871: arch/openrisc] Error 2
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
/bin/bash: scripts/pahole-flags.sh: No such file or directory
make[1]: *** [Makefile:1871: security] Error 2
make[1]: *** [Makefile:1871: mm] Error 2
make[1]: *** [Makefile:1871: block] Error 2
make[1]: *** [Makefile:1871: kernel] Error 2
make[1]: *** [Makefile:1871: net] Error 2
make[1]: *** [Makefile:1871: lib] Error 2
make[1]: *** [Makefile:1871: fs] Error 2
make[1]: *** [Makefile:1871: drivers] Error 2
make[1]: *** [Makefile:1871: sound] Error 2
make[1]: Target '__all' not remade because of errors.
--
>> /bin/bash: scripts/pahole-flags.sh: No such file or directory
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32669 bytes --]
next prev parent reply other threads:[~2021-10-27 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 21:24 [PATCHv2 bpf-next] kbuild: Unify options for BTF generation for vmlinux and modules Jiri Olsa
2021-10-27 13:44 ` kernel test robot
2021-10-27 14:57 ` kernel test robot [this message]
2021-10-28 17:14 ` Jiri Olsa
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=202110272241.3Njacivm-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.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).