All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH bpf-next v2 8/8] selftests/bpf: Avoid static LLVM linking for cross builds
Date: Tue, 2 Jun 2026 23:00:09 +0200	[thread overview]
Message-ID: <202606022207.PcDtt93e-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260602-tools_build_fix_zero_init_bpf_only-v2-8-c76e5250ea1c@arm.com>
References: <20260602-tools_build_fix_zero_init_bpf_only-v2-8-c76e5250ea1c@arm.com>
TO: Leo Yan <leo.yan@arm.com>
TO: Quentin Monnet <qmo@kernel.org>
TO: Alexei Starovoitov <ast@kernel.org>
TO: Daniel Borkmann <daniel@iogearbox.net>
TO: Andrii Nakryiko <andrii@kernel.org>
TO: Martin KaFai Lau <martin.lau@linux.dev>
TO: Eduard Zingerman <eddyz87@gmail.com>
TO: Song Liu <song@kernel.org>
TO: Yonghong Song <yonghong.song@linux.dev>
TO: John Fastabend <john.fastabend@gmail.com>
TO: KP Singh <kpsingh@kernel.org>
TO: Stanislav Fomichev <sdf@fomichev.me>
TO: Hao Luo <haoluo@google.com>
TO: Jiri Olsa <jolsa@kernel.org>
TO: Shuah Khan <skhan@linuxfoundation.org>
TO: Lorenz Bauer <lmb@isovalent.com>
TO: Nathan Chancellor <nathan@kernel.org>
TO: Nick Desaulniers <nick.desaulniers+lkml@gmail.com>
TO: Bill Wendling <morbo@google.com>
TO: Justin Stitt <justinstitt@google.com>
CC: Arnaldo Carvalho de Melo <acme@kernel.org>
CC: Namhyung Kim <namhyung@kernel.org>
CC: Ian Rogers <irogers@google.com>
CC: James Clark <james.clark@linaro.org>
CC: Kees Cook <kees@kernel.org>
CC: bpf@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-kselftest@vger.kernel.org
CC: llvm@lists.linux.dev
CC: Leo Yan <leo.yan@arm.com>

Hi Leo,

kernel test robot noticed the following build warnings:

[auto build test WARNING on b93c55b4932dd7e32dca8cf34a3443cc87a02906]

url:    https://github.com/intel-lab-lkp/linux/commits/Leo-Yan/bpftool-Pass-host-flags-to-bootstrap-libbpf/20260602-231100
base:   b93c55b4932dd7e32dca8cf34a3443cc87a02906
patch link:    https://lore.kernel.org/r/20260602-tools_build_fix_zero_init_bpf_only-v2-8-c76e5250ea1c%40arm.com
patch subject: [PATCH bpf-next v2 8/8] selftests/bpf: Avoid static LLVM linking for cross builds
:::::: branch date: 6 hours ago
:::::: commit date: 6 hours ago
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260602/202606022207.PcDtt93e-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260602/202606022207.PcDtt93e-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202606022207.PcDtt93e-lkp@intel.com/

All warnings (new ones prefixed by >>):

   Makefile.config:577: No elfutils/debuginfod.h found, no debuginfo server support, please install libdebuginfod-dev/elfutils-debuginfod-client-devel or equivalent
   Makefile.config:964: No libllvm 13+ found, slower source file resolution, please install llvm-devel/llvm-dev
   Makefile.config:1160: Rust is not found. Test workloads with rust are disabled.
     PERF_VERSION = 7.1.rc5.g381f7c643a0a
>> cc1: warning: '-Wformat-y2k' ignored without '-Wformat' [-Wformat-y2k]
>> cc1: warning: '-Wformat-security' ignored without '-Wformat' [-Wformat-security]
   builtin-trace.c: In function 'syscall_arg__strtoul_btf_enum':
   builtin-trace.c:967:27: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
     967 |         for (int i = 0; i < btf_vlen(bt); ++i, ++be) {
         |                           ^
   util/btf.c: In function '__btf_type__find_member_by_name':
   util/btf.c:19:43: error: comparison of integer expressions of different signedness: 'int' and '__u32' {aka 'unsigned int'} [-Werror=sign-compare]
      19 |         for (i = 0, m = btf_members(t); i < btf_vlen(t); i++, m++) {
         |                                           ^
   cc1: all warnings being treated as errors
   make[4]: *** [tools/build/Makefile.build:95: util/btf.o] Error 1
   make[4]: *** Waiting for unfinished jobs....
   cc1: all warnings being treated as errors
   make[3]: *** [tools/build/Makefile.build:95: builtin-trace.o] Error 1
   make[3]: *** Waiting for unfinished jobs....
   make[3]: *** [tools/build/Makefile.build:158: util] Error 2
   make[2]: *** [Makefile.perf:802: perf-util-in.o] Error 2
   make[2]: *** Waiting for unfinished jobs....
   make[2]: *** [Makefile.perf:775: perf-in.o] Error 2
   make[1]: *** [Makefile.perf:288: sub-make] Error 2

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-06-02 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 21:00 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-02 14:47 [PATCH bpf-next v2 0/8] tools build: bpf: Append EXTRA_CFLAGS and HOST_EXTRACFLAGS Leo Yan
2026-06-02 14:47 ` [PATCH bpf-next v2 8/8] selftests/bpf: Avoid static LLVM linking for cross builds Leo Yan
2026-06-02 17:33   ` sashiko-bot

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=202606022207.PcDtt93e-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.