linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Networking <netdev@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jiri Olsa <jolsa@kernel.org>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
Date: Tue, 14 Jul 2020 10:31:33 +0200	[thread overview]
Message-ID: <20200714083133.GF183694@krava> (raw)
In-Reply-To: <20200714061654.GE183694@krava>

On Tue, Jul 14, 2020 at 08:16:54AM +0200, Jiri Olsa wrote:
> On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the bpf-next tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > tmp/ccsqpVCY.s: Assembler messages:
> > tmp/ccsqpVCY.s:78: Error: unrecognized symbol type ""
> > tmp/ccsqpVCY.s:91: Error: unrecognized symbol type ""
> > 
> > I don't know what has caused this (I guess maybe the resolve_btfids
> > branch).
> > 
> > I have used the bpf-next tree from next-20200713 for today.
> 
> ok, trying to reproduce

damn crossbuilds.. change below fixes it for me,
will do some more testing and post it today

jirka


---
diff --git a/include/linux/btf_ids.h b/include/linux/btf_ids.h
index fe019774f8a7..8b9194e22c7c 100644
--- a/include/linux/btf_ids.h
+++ b/include/linux/btf_ids.h
@@ -21,7 +21,7 @@
 asm(							\
 ".pushsection " BTF_IDS_SECTION ",\"a\";       \n"	\
 ".local " #symbol " ;                          \n"	\
-".type  " #symbol ", @object;                  \n"	\
+".type  " #symbol ", STT_OBJECT;               \n"	\
 ".size  " #symbol ", 4;                        \n"	\
 #symbol ":                                     \n"	\
 ".zero 4                                       \n"	\
diff --git a/tools/bpf/resolve_btfids/Makefile b/tools/bpf/resolve_btfids/Makefile
index 948378ca73d4..a88cd4426398 100644
--- a/tools/bpf/resolve_btfids/Makefile
+++ b/tools/bpf/resolve_btfids/Makefile
@@ -16,6 +16,20 @@ else
   MAKEFLAGS=--no-print-directory
 endif
 
+# always use the host compiler
+ifneq ($(LLVM),)
+HOSTAR  ?= llvm-ar
+HOSTCC  ?= clang
+HOSTLD  ?= ld.lld
+else
+HOSTAR  ?= ar
+HOSTCC  ?= gcc
+HOSTLD  ?= ld
+endif
+AR       = $(HOSTAR)
+CC       = $(HOSTCC)
+LD       = $(HOSTLD)
+
 OUTPUT ?= $(srctree)/tools/bpf/resolve_btfids/
 
 LIBBPF_SRC := $(srctree)/tools/lib/bpf/


  reply	other threads:[~2020-07-14  8:31 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  2:22 linux-next: build failure after merge of the bpf-next tree Stephen Rothwell
2020-07-14  6:16 ` Jiri Olsa
2020-07-14  8:31   ` Jiri Olsa [this message]
2020-07-14  9:19     ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2023-03-19 23:26 Stephen Rothwell
2023-03-20 12:07 ` Alexander Lobakin
2023-03-21 22:35   ` Stephen Rothwell
2022-07-20  1:59 Stephen Rothwell
2022-07-20  3:42 ` Alexei Starovoitov
2022-07-20  3:44   ` Stanislav Fomichev
2022-04-19  1:56 Stephen Rothwell
2022-04-21  0:32 ` Stephen Rothwell
2022-04-21  9:45   ` Daniel Borkmann
2022-04-21 10:40     ` Maciej Fijalkowski
2022-02-09  0:21 Stephen Rothwell
2021-12-03  0:15 Stephen Rothwell
2021-09-14  1:37 Stephen Rothwell
2021-09-14 23:25 ` Andrii Nakryiko
2021-09-14 23:38   ` Stephen Rothwell
2021-09-14 23:40     ` Andrii Nakryiko
2021-09-14 23:59       ` Stephen Rothwell
2021-09-15  1:27         ` Alexei Starovoitov
2021-08-26  1:50 Stephen Rothwell
2021-08-26  2:01 ` Daniel Xu
2021-03-11  0:47 Stephen Rothwell
2021-03-11  6:47 ` Björn Töpel
2021-03-12  1:00   ` Stephen Rothwell
2021-03-26  1:18     ` Stephen Rothwell
2020-12-01  8:07 Stephen Rothwell
2020-12-01 14:55 ` Daniel Borkmann
2020-09-08  3:08 Stephen Rothwell
2020-09-08 17:54 ` Andrii Nakryiko
2020-08-21  1:11 Stephen Rothwell
2020-08-25  1:20 ` Stephen Rothwell
2020-08-25  1:25   ` Alexei Starovoitov
2020-08-25  3:04     ` Stephen Rothwell
2020-08-25  3:27       ` Alexei Starovoitov
2020-08-25  6:50         ` Stephen Rothwell
2020-08-25 14:33           ` Alexei Starovoitov
2020-08-25 21:10             ` Stephen Rothwell
2020-08-25 22:34               ` Alexei Starovoitov
2020-08-25 23:09                 ` Stephen Rothwell
2019-07-01  4:57 Stephen Rothwell
2019-07-01  5:01 ` Stephen Rothwell
2019-04-18  1:57 Stephen Rothwell
2019-02-28  1:31 Stephen Rothwell
2019-02-28  2:18 ` Alexei Starovoitov
2018-10-03  3:18 Stephen Rothwell
2018-10-03  5:29 ` Joe Stringer
2018-09-07  0:19 Stephen Rothwell
2018-09-07  0:22 ` Alexei Starovoitov
2018-09-07  5:21   ` Björn Töpel
2018-09-07  5:45     ` Alexei Starovoitov
2017-12-13  1:32 Stephen Rothwell
2017-12-13  1:47 ` Alexei Starovoitov

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=20200714083133.GF183694@krava \
    --to=jolsa@redhat.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.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).