linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-perf-users@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Leo Yan <leo.yan@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: Tree for Nov 20
Date: Wed, 20 Nov 2019 16:52:28 +0530	[thread overview]
Message-ID: <CA+G9fYufQjPVsDATdyDn+xtxD1FrwnVGKJ+bpVAxvoropJ=7hg@mail.gmail.com> (raw)
In-Reply-To: <20191120203434.2a0727b3@canb.auug.org.au>

Perf build failed on linux next for i386 and armv7.

On Wed, 20 Nov 2019 at 15:04, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Changes since 20191119:
>
> The net tree gained a conflict against Linus' tree.
>
> Non-merge commits (relative to Linus' tree): 11697
>  10361 files changed, 506041 insertions(+), 224327 deletions(-)

i386 build failed log,
---------------------------
 In file included from libbpf.c:52:0:
 libbpf.c: In function 'bpf_program__collect_reloc':
 libbpf_internal.h:59:22: error: format '%lu' expects argument of type
 'long unsigned int', but argument 3 has type 'Elf64_Addr {aka long
long unsigned int}' [-Werror=format=]
   libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__); \
                       ^
 libbpf_internal.h:62:27: note: in expansion of macro '__pr'
  #define pr_warn(fmt, ...) __pr(LIBBPF_WARN, fmt, ##__VA_ARGS__)
                            ^~~~
 libbpf.c:1874:5: note: in expansion of macro 'pr_warn'
      pr_warn("bad call relo offset: %lu\n", sym.st_value);
      ^~~~~~~
 libbpf.c:1874:38: note: format string is defined here
      pr_warn("bad call relo offset: %lu\n", sym.st_value);
                                     ~~^
                                     %llu
 Makefile:652: arch/x86/Makefile: No such file or directory
 cc1: all warnings being treated as errors

 find: unknown predicate `-m32/arch'

 Try 'find --help' for more information.
   CC       perf/1.0-r9/perf-1.0/staticobjs/libbpf_probes.o
 i686-linaro-linux-gcc: warning: '-x c' after last input file has no effect
   CC       perf/1.0-r9/perf-1.0/staticobjs/xsk.o
 i686-linaro-linux-gcc: error: unrecognized command line option
'-m32/include/uapi/asm-generic/errno.h'
 i686-linaro-linux-gcc: fatal error: no input files
 compilation terminated.

arm build log:
------------------
 Makefile:652: arch/arm/Makefile: No such file or directory
 In file included from libbpf.c:52:0:
 libbpf.c: In function 'bpf_program__collect_reloc':
 libbpf_internal.h:59:22: error: format '%lu' expects argument of type
 'long unsigned int', but argument 3 has type 'Elf64_Addr {aka long
long unsigned int}' [-Werror=format=]
   libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__); \
                       ^
 libbpf_internal.h:62:27: note: in expansion of macro '__pr'
  #define pr_warn(fmt, ...) __pr(LIBBPF_WARN, fmt, ##__VA_ARGS__)
                            ^~~~
 libbpf.c:1874:5: note: in expansion of macro 'pr_warn'
      pr_warn("bad call relo offset: %lu\n", sym.st_value);
      ^~~~~~~
 libbpf.c:1874:38: note: format string is defined here
      pr_warn("bad call relo offset: %lu\n", sym.st_value);
                                     ~~^
                                     %llu

ref:
https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=intel-core2-32,label=docker-lkft/650/consoleText
https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=am57xx-evm,label=docker-lkft/650/consoleText

- Naresh

  reply	other threads:[~2019-11-20 11:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  9:34 linux-next: Tree for Nov 20 Stephen Rothwell
2019-11-20 11:22 ` Naresh Kamboju [this message]
2019-11-20 16:18 ` linux-next: Tree for Nov 20 (kcsan + objtool) Randy Dunlap
2019-11-20 19:48   ` Marco Elver
2019-11-21 18:37     ` Josh Poimboeuf
2019-11-21 18:43       ` Marco Elver
2019-11-22 15:48         ` Marco Elver
2020-03-24  9:11   ` [tip: locking/kcsan] kcsan: Prefer __always_inline for fast-path tip-bot2 for Marco Elver
  -- strict thread matches above, loose matches on Subject: below --
2023-11-20  6:07 linux-next: Tree for Nov 20 Stephen Rothwell
2020-11-20  5:56 Stephen Rothwell
2020-11-20 11:57 ` Sudip Mukherjee
2020-11-20 13:41   ` Thomas Bogendoerfer
2018-11-20  5:02 Stephen Rothwell
2017-11-20  3:45 Stephen Rothwell
2015-11-20  4:17 Stephen Rothwell
2014-11-20  7:46 Stephen Rothwell
2014-11-20 14:46 ` Guenter Roeck
2013-11-20  2:28 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+G9fYufQjPVsDATdyDn+xtxD1FrwnVGKJ+bpVAxvoropJ=7hg@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=acme@kernel.org \
    --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=mhiramat@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).