From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Will Deacon <will@kernel.org>
Subject: [linux-next:master 4737/7019] __pi_fdt.c:undefined reference to `__pi___memmove'
Date: Fri, 1 Jul 2022 04:25:29 +0800 [thread overview]
Message-ID: <202207010445.YbThcxfw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6cc11d2a1759275b856e464265823d94aabd5eaf
commit: aacd149b62382c63911060b8f64c1e3d89bd405a [4737/7019] arm64: head: avoid relocating the kernel twice for KASLR
config: arm64-randconfig-r013-20220630 (https://download.01.org/0day-ci/archive/20220701/202207010445.YbThcxfw-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.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/next/linux-next.git/commit/?id=aacd149b62382c63911060b8f64c1e3d89bd405a
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout aacd149b62382c63911060b8f64c1e3d89bd405a
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 6cc11d2a1759275b856e464265823d94aabd5eaf builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
aarch64-linux-ld: arch/arm64/kernel/pi/lib-fdt.pi.o: in function `__pi_fdt_move':
>> __pi_fdt.c:(.init.text+0x63c): undefined reference to `__pi___memmove'
__pi_fdt.c:(.init.text+0x63c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__pi___memmove'
aarch64-linux-ld: arch/arm64/kernel/pi/lib-fdt_ro.pi.o: in function `__pi_fdt_get_path':
>> __pi_fdt_ro.c:(.init.text+0xca0): undefined reference to `__pi___memcpy'
__pi_fdt_ro.c:(.init.text+0xca0): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__pi___memcpy'
aarch64-linux-ld: .tmp_vmlinux.kallsyms1: hidden symbol `__pi___memcpy' isn't defined
aarch64-linux-ld: final link failed: bad value
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-30 20:26 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=202207010445.YbThcxfw-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=will@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