From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jolsa-perf:bpf/ftrace 2/6] arm-linux-gnueabi-ld: syscall.c:undefined reference to `__bpf_prog_exit'
Date: Tue, 13 Apr 2021 12:03:04 +0800 [thread overview]
Message-ID: <202104131259.vSKD0Ffe-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/ftrace
head: f6ca0faab8697bc6a3a6e4ffcb72b8a0a0a66558
commit: e201e5e6b442644c28e6c9a001ef2b7e4428aa51 [2/6] bpf: Add bpf ftrace link
config: arm-aspeed_g4_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git/commit/?id=e201e5e6b442644c28e6c9a001ef2b7e4428aa51
git remote add jolsa-perf https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
git fetch --no-tags jolsa-perf bpf/ftrace
git checkout e201e5e6b442644c28e6c9a001ef2b7e4428aa51
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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 >>):
arm-linux-gnueabi-ld: kernel/bpf/syscall.o: in function `bpf_ftrace_function_call':
syscall.c:(.text+0xbd8): undefined reference to `__bpf_prog_enter'
>> arm-linux-gnueabi-ld: syscall.c:(.text+0xbf8): undefined reference to `__bpf_prog_exit'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 24368 bytes --]
reply other threads:[~2021-04-13 4:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202104131259.vSKD0Ffe-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.