From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: kbuild-all@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org
Subject: [djwong-xfs:djwong-wtf 399/400] hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3fee8): cannot reach 00005b1d___trace_trigger_soft_disabled+0, recompile with -ffunction-sections
Date: Thu, 14 Apr 2022 03:59:42 +0800 [thread overview]
Message-ID: <202204140330.biy5ckQP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git djwong-wtf
head: 4b24106233a017435a70bc0e8ff7afbaddd479d6
commit: ff88d33413f541442f302e44b95dfdc08a52e415 [399/400] xfs: fallocate free space into a file
config: parisc-allyesconfig (https://download.01.org/0day-ci/archive/20220414/202204140330.biy5ckQP-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.2.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/djwong/xfs-linux.git/commit/?id=ff88d33413f541442f302e44b95dfdc08a52e415
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs djwong-wtf
git checkout ff88d33413f541442f302e44b95dfdc08a52e415
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc SHELL=/bin/bash
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 >>):
>> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3fee8): cannot reach 00005b1d___trace_trigger_soft_disabled+0, recompile with -ffunction-sections
>> hppa-linux-ld: fs/xfs/xfs_trace.o(.text+0x3fee8): cannot handle R_PARISC_PCREL17F for __trace_trigger_soft_disabled
hppa-linux-ld: final link failed: bad value
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-13 20:00 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=202204140330.biy5ckQP-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).